Some questions about updated team space and the corresponding api change

Hi, thanks again for your feedback. I just wanted to jump in here to confirm that we've shared this with the team, including a request to extend the timeline. I can't promise if the timeline will be extended, but I'll be sure to follow up here if there's any news on that.

Also, in case it helps, I wanted to clarify a things:

• Apps can and should continue to use the /2/files endpoints to work with files and folders; the exception is that accounts on teams with the updated team space can't create anything directly in the root of the team space, but they can continue to create and update things inside the team folders in the team space using the existing /2/files endpoints. For example, attempting to upload a file directly in the team space for an account on a team with the updated team space would fail with the existing path/no_write_permission error that is already used for other cases where the account does not have permission to upload a file in the specified location. Apps can upload files inside an existing team folder in the team space for an account on a team with the updated team space though.
• In order to create new team folders, which would be placed in the team space for accounts on teams with the updated team space, an app would need to use /2/team/team_folder/create, which is the same way apps would already create team folders for teams without a team space.
• For any kind of account, apps can still and should continue to get the root_namespace_id from /2/users/get_current_account. Likewise, apps can continue to use that value in the Dropbox-Api-Path-Root header, whether the account is on a team or not, and regardless of what configuration the team has. That will also work for accounts on teams with the updated team space.
• The API will continue to work the same way for teams on the old configurations; there won't be any impact for teams before they are migrated to the updated team space.