You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Access team folders - Old Business Team Configuration
I understand that with the new team spaces and namespace configurations, that we would have to use 'Dropbox-API-Path-Root' header and I've managed to get it working by setting the namespace to the ro...
Yes, on the Dropbox Business API, you can use the /2/team/features/get_values endpoint to check the 'has_team_shared_dropbox' feature to see if the team uses the team space configuration.
Or, on the Dropbox API, you can call /2/users/get_current_account and check the returned RootInfo type to see if the user is a member of a team that uses the team space configuration. Specifically, the returned 'root_info' will be a 'UserRootInfo' (with '.tag' of 'user') if the team doesn't use the team space, or a 'TeamRootInfo' (with a '.tag' of 'team') if it does.
If you're using the "team member file access" feature, and want to operate on a particular user only, you should use the "Dropbox-API-Select-User" header. (The "Dropbox-API-Select-Admin" header is for access any team owned content in general.) And for listing any/all files in a user's account, you should use /2/files/list_folder[/continue]. (The /2/sharing/list_folders[/continue] endpoints, on the other hand, only list the shared folders in particular, and not their contents.)
Greg-DB
Dropbox Staff
Dropbox StaffWe unfortunately don't have a way for developers to get test accounts like this, with this feature toggle-able, but I'll pass this along as a feature request.
For reference, I do recommend reviewing the Namespace Guide and Content Access Guide, if you haven't already, as they are good references for this.
In accounts on teams that don't use the "team space" configuration, any team folders that an account has access to are "mounted" in the account's root. That means that using list_folder[_continue] to list the root (using the empty string "" as the path value) will list both their personal folders as well as the team folders they have. Make sure you do check the has_more value returned by list_folder though, to see if you need to call back to list_folder_continue, and so on, to get more entries.
Hi,
I would like to add on to this question, is there an API that we can call to determine whether a particular dropbox business team's folder has the "team space" configuration or not and thus add the 'Dropbox-API-Select-Admin' and set the namespace accordingly on the subsequent calls?
Also, by calling 'list_folders' on the accounts of those who do not have the "team space" configuration, would I be able to get all the other member's personal folders as well should I have the ''Dropbox-API-Select-Admin' header.
Basically what I want to achieve is regardless of whether a team has the "team space" configuration or not, to grab a list of all the files and folders of all users and teams.
- Greg-DB
Yes, on the Dropbox Business API, you can use the /2/team/features/get_values endpoint to check the 'has_team_shared_dropbox' feature to see if the team uses the team space configuration.
Or, on the Dropbox API, you can call /2/users/get_current_account and check the returned RootInfo type to see if the user is a member of a team that uses the team space configuration. Specifically, the returned 'root_info' will be a 'UserRootInfo' (with '.tag' of 'user') if the team doesn't use the team space, or a 'TeamRootInfo' (with a '.tag' of 'team') if it does.
If you're using the "team member file access" feature, and want to operate on a particular user only, you should use the "Dropbox-API-Select-User" header. (The "Dropbox-API-Select-Admin" header is for access any team owned content in general.) And for listing any/all files in a user's account, you should use /2/files/list_folder[/continue]. (The /2/sharing/list_folders[/continue] endpoints, on the other hand, only list the shared folders in particular, and not their contents.)
So would it be right to say that if I were to list down all the folders of the dropbox business account (the old configuration) in a way that it is displayed like the following:
- /User1
- User1/FolderA
- User1/FolderB/FileZ
- User1/FileA
- /User2
- User2/FileA
- /SharedFolder1
- /SharedFolder1/FileA
- /SharedFolder2
- /SharedFolder2/FileB
I would have to go through the member's list and do a "files/list_folder" using all the different member's ID entered in "Dropbox-API-Select-User" and then merge it into a full list?
I am asking this because for the new configuration, I can just do a "Dropbox-API-Path-Root" with the root namespace and do a "files/list_folder" while using "Dropbox-API-Select-Admin".
Is there an easier way to go about doing it for the old configuration?
- Greg-DB
That's correct, and no, unfortunately there isn't really an easier way to do that with the old configuration. (You may want to look into using /2/team/namespaces/list[/continue] and listing by each namespace though; that may streamline it, depending on what you're looking to do exactly.)
- /User1
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
