We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
team data.member permission implicitly checked team data.governance.write
I am configuring App client with Dropbox.
In Permission tab, when i checked team data.member permission, it implicitly checked team data.governance.write. Is this bug ?
I just want configure pe...
Hello Megan,
I want to get all groups & user information with read-only permission only.
So when click on "groups.read" only , it gives me error as ,
But Combining Team and User scopes requires team_data.member.
So i have to check team_data.member checkbox which implicitly enable team data.governance.write and i dont want any write permission.
Greg-DB
Dropbox Staff
Dropbox StaffThis is the expected behavior; the team_data.member scope has a dependency on the team_data.governance.write scope so the team_data.governance.write scope is required if/when you enable the team_data.member scope.
This is a bad implementation. If I want a read-only integration with access to read team info, why should I be forced to grant a very permissive write scope such as the team_data.governance.write? Would love to hear the explanation of such behavior, and if this has any workaround that does not require write scope.
- Greg-DB
maimon Thanks for the feedback! I'll pass this along to the team. I don't have more information to share on this scope dependency, and unfortunately there isn't a workaround for this; if you enable team_data.member that will automatically require team_data.governance.write. If I get an update on this though, I'll share it here.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
