We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Ashley B.15
6 years agoHelpful | Level 7
Remove Shared Folder Invitee
I've been working on Sharing of folders using the API, but can not see how you remove a member who has not added it to their dropbox
This is the message in the UI "name@domain.com has not added thi...
- 6 years ago
The /2/sharing/remove_folder_member endpoint (or corresponding native method) would be the right way to remove a member from a folder, whether or not they've mounted it. (Or, if operating on the recipient themselves, /2/sharing/relinquish_folder_membership.)
That 'no_explicit_access' error should indicate "The target member only has inherited access to the shared folder". For example, they only have access by virtue of having access to a higher level folder, meaning you can't remove just the lower folder.
Can you print out the full error object/message? The nested `MemberAccessLevelResult` may contain more useful information.
If that doesn't seem to be the case though, please share some sample calls that produce this unexpected error though so we can look into it.
Also, sharing individual files is a different piece of functionality than sharing folders, and sharing individual files does only support view-only access. For that, you can add members to files using /2/sharing/add_file_member, and remove them using /2/sharing/remove_file_member_2.
Greg-DB
Dropbox Staff
The /2/sharing/remove_folder_member endpoint (or corresponding native method) would be the right way to remove a member from a folder, whether or not they've mounted it. (Or, if operating on the recipient themselves, /2/sharing/relinquish_folder_membership.)
That 'no_explicit_access' error should indicate "The target member only has inherited access to the shared folder". For example, they only have access by virtue of having access to a higher level folder, meaning you can't remove just the lower folder.
Can you print out the full error object/message? The nested `MemberAccessLevelResult` may contain more useful information.
If that doesn't seem to be the case though, please share some sample calls that produce this unexpected error though so we can look into it.
Also, sharing individual files is a different piece of functionality than sharing folders, and sharing individual files does only support view-only access. For that, you can add members to files using /2/sharing/add_file_member, and remove them using /2/sharing/remove_file_member_2.
Ashley B.15
6 years agoHelpful | Level 7
Hi,
Thanks for the reply, and it was the parent that had the permission also.
I get the following error now :
HTTP/1.1 409 Conflict
X-Dropbox-Request-Id: 860311efbc28a9b13e0ee1bb5d4e7ddd
{"error_summary": "internal_error/.", "error": {".tag": "internal_error"}}
I am retrying and still fails. Does the request Id help?
Thanks
- Greg-DB6 years agoDropbox Staff
What kind of job are you trying to check when you get this?
For example, if you're sharing a folder using /2/sharing/share_folder, per the docs you should check on the job with /2/sharing/check_share_job_status.
Or, if you're unsharing a folder using /2/sharing/unshare_folder, you need to check on the job using /2/sharing/check_job_status. (Note the difference between check_share_job_status and check_job_status.)
If you're using an SDK, there are corresponding native methods for each of these.
- Ashley B.156 years agoHelpful | Level 7
Yep, that would be the problem. I was calling CheckShareJobStatus for UnSharing a folder.
Thanks for your help.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
5,877 PostsLatest Activity: 12 months 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!