team data.member permission implicitly checked team data.governance.write

Hey sagar_lonkar, I hope you're doing well!

Would you mind clarifying for me if you use an API on your end when you see the above? 

If you have any screenshots, feel free to send it our way, in order for us to have a visual.

Keep me posted! 

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.

I see, it sounds like our API section in the Community might be more helpful sharing any additional info with you, so I am going to be moving your message there sagar_lonkar. 

This 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.

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.