We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Syno_dev
12 months agoHelpful | Level 5
Some questions about updated team space and the corresponding api change
Hi, we've received an email last week saying that "shared team space" is gonna be updated to "updated team space" https://dropbox.tech/developers/api-updates-to-better-support-team-spaces We've rea...
DB-Des
Dropbox Engineer
Hi there,
We appreciate your feedback, I’ll be sure to bring this up with the team for review.
To address some of your concerns:
- Dropbox is not making changes to the behavior of the API for teams with the previous configurations. The API behaves differently for teams with the latest configuration however, and Dropbox plans to eventually migrate all teams to the latest configuration, which is why we've made this announcement. The deadline for this update is still set to be for 2024/01/31.
- With the new configuration, every team member will have their own unique root_namespace_id. This ID can be obtained by calling /users/get_current_account, and should be set properly for each user the app is operating on as the value for Dropbox-Api-Path-Root.
- Files and folders may not be added directly to the root of a team space using the /2/files endpoints. For folder creation, app can use /2/team/team_folder/create.
- Team endpoints are Business Endpoints, thus team scopes will be needed to utilize these endpoints. Existing access tokens will retain only whatever scopes they were originally granted. If the app needs additional scopes for any particular account, it will need to prompt the user to process the app authorization flow again with the additional scopes. The user will then receive a new access token with the additional scopes granted.
Syno_dev
12 months agoHelpful | Level 5
Hi, thank you for your reply.
I'm wondering what it means by "Dropbox plans to eventually migrate all teams to the latest configuration". Are the original teams with "shared team space" configurations still gonna be migrated to new "updated team space" configuration? Or will they just stay the same, and will never be updated to "updated team space", only the teams after 2024/01/31 will have new configurations?
If the old "shared team space" configuration will be updated to "updated team space", will the deadline also be 2024/01/31, or will it be extended?
Moreover, will we get access to "updated team space" account for development? If the deadline is surely 2024/01/31, it is almost impossible for us to finish migration before then. We'll have to just start as soon as possible.
- DB-Des12 months agoDropbox Engineer
Hi,
Are the original teams with "shared team space" configurations still gonna be migrated to new "updated team space" configuration? Or will they just stay the same, and will never be updated to "updated team space", only the teams after 2024/01/31 will have new configurations?
All existing teams will be migrated to the new team space configuration. Any newly-created teams will be defaulted to the new team space configuration.
If the old "shared team space" configuration will be updated to "updated team space", will the deadline also be 2024/01/31, or will it be extended?
The plan, currently, is still to have all existing teams migrated by 2024/01/31.
Moreover, will we get access to "updated team space" account for development? If the deadline is surely 2024/01/31, it is almost impossible for us to finish migration before then. We'll have to just start as soon as possible.
If you'd like to request a test team using the updated team space configuration, you can do so by following the instructions under "How do I test my application?" in the "Frequently asked questions" list here: https://www.dropbox.com/developers/support . Be sure to indicate why you are requesting that and specifically mention that you want a team with the updated team space configuration.
I hope you find this additional information helpful!
- Syno_dev12 months agoHelpful | Level 5
Hi,thank you for your reply
Our application used to use team space root for syncing. However, if the configuration is going to change dramitically, we just can't use team space root any more. We'll have to sync from team folder, this will require us to modify bunch of apis.
Do you recommend other faster way to tune the architecture? If not, 2024/01/31 is just too urgent to adopt the change.
Our application will fail to sync then for all users with old shared team space configuration. Unless we have enough time to import reauth flow and change files api to teams api in order to create/rename/archive/delete team folders.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
5,877 PostsLatest Activity: 5 hours agoIf you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!