We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
Cannot find a way to have a restricted API access to a team-shared folder
Hello, I have an accounting system for which we'd like to leverage our Dropbox Business subscription. What I need is a Dropbox folder, shared with specific members only, and a way to create a Dropb...
Ultimately it worked out fine. I indeed used the trick in point #3, then:
- POST /2/users/get_current_account (with an auth token for the restricted user) then fetch root_info/root_namespace_id
- from there, add the header:
Dropbox-Api-Path-Root set to {".tag": "namespace_id", "namespace_id": the_root_namespace_id}
- fetch using /2/files/list_folder (and continue version)
This allows restricted access to a team-shared folder.
Now a word of feedback: I really hope in the future it will be possible to avoid the creation of a specific user & restrictions, and instead have Dropbox provide an additional level of access (instead of Full Dropbox vs. User-Specific-Folder) to allow access to a restricted list of folders.
In all cases, thanks for your help, which put me on good track!
-- Thibaut
chirstius
Dropbox Staff
Dropbox StaffHey thbar,
When you say the app can only see it's own documents and not the company (team) shared folder for #3 do you mean, literally the listing does not contain ANY team folder content at all? As if it didn't exist?
If so, you may be using team space and member folders and would need to access the team content a little bit differently. You should take a read through the Namespace Guide for information about how to get the root namespace and accessing team content. That may get you where you want to be.
-Chuck
Hello Chuck,
> When you say the app can only see it's own documents and not the company (team) shared folder for #3 do you mean, literally the listing does not contain ANY team folder content at all? As if it didn't exist?
It's exactly that. It can see its own documents (currently "get started with dropbox pdf"), and nothing else.
Thanks for your quick feedback, I'm diving into the namespacing documentation & playing around with the PAW API client, to see if I can figure out how to get what I need here.
Will report back :-)
-- Thibaut
- chirstius
Sounds like that might be the case then. If you have additional questions just post them back, but once you get the root namespace, and add the path root header to your requests, I think you'll be in a good place.
Good luck!
-Chuck
Ultimately it worked out fine. I indeed used the trick in point #3, then:
- POST /2/users/get_current_account (with an auth token for the restricted user) then fetch root_info/root_namespace_id
- from there, add the header:
Dropbox-Api-Path-Root set to {".tag": "namespace_id", "namespace_id": the_root_namespace_id}
- fetch using /2/files/list_folder (and continue version)
This allows restricted access to a team-shared folder.
Now a word of feedback: I really hope in the future it will be possible to avoid the creation of a specific user & restrictions, and instead have Dropbox provide an additional level of access (instead of Full Dropbox vs. User-Specific-Folder) to allow access to a restricted list of folders.
In all cases, thanks for your help, which put me on good track!
-- Thibaut
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
