We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
How to create a folder in a team shared folder and make it accessible to a small part of the team
Hi, I am currently using Make (a no code platform) to automate the creation of a folder in a shared folder after the start of a new project. The issue is that everyone (30 ~) have access to that fol...
Hi Здравко,
So after the creation of the folder, I need to share it through this endpoint
https://api.dropboxapi.com/2/sharing/share_folder
with the
"access_inheritance": "no_inherit"
in the body of the request,
I will then use this endpoint
https://api.dropboxapi.com/2/sharing/add_folder_member
with all the members that need to access that folder in the body
Yes, that's one of the scenarios I mentioned above (when you are nesting shared folders and need to exclude derived/inherited access - when parent folder has more members than needed).
Poui wrote:Hi Здравко,
So after the creation of the folder, I need to share it ...
By the way, you can do it in one call. When you share a non existing folder, it's created automatically. 😉
Hi, thanks again for your help but I have two questions.
1. When I try to share a non-existing folder, i get this error instead of it creating like you said :{ "error_summary": "no_permission/...", "error": { ".tag": "no_permission" }, "user_message": { "locale": "en", "text": "You don’t have permission to perform this action." } }2. despite removing the access inheritance of the folder, my team still have a folder on their dropbox explorer of that folder. It doesn't disappear.
To be honest I can't reproduce that. It works for me. Are you sure the context you're representing, in your call, really has access permission there? 🤔 You may need admin access! Who is the owner of the parent folder and if that's not you, as a member, what access you have?
- Greg-DB
Dropbox Staff
Poui 2. If you create a shared folder without inheritance in a team folder, the other members will still see the nested shared folder itself; they just won't be able to access its contents.
If that's not the behavior you want, you may want to create the shared folder outside the team folder.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
