Forum Discussion
Issue with Teams RSC Permission TeamMember.Read.Group
MicrosoftRSC permissions only work for standard channels. To manage private/shared channel members, you must use broader Graph permissions with admin consent. This is a platform limitation, not a configuration issue.
Why doesn’t ChannelMember.ReadWrite.Group work for private/shared channels?
- RSC permissions (like ChannelMember.ReadWrite.Group) are designed for standard (public) channels only.
- Private channels and shared channels have separate membership and stricter security boundaries. The RSC model does not grant bots/applications access to manage or read members of private/shared channels, even if the app is installed at the team level.
The error messages you see are expected:
- For private channels, you need Directory-wide or Group-wide permissions (e.g., ChannelMember.ReadWrite.All, Group.ReadWrite.All), which are not RSC and require admin consent.
- For shared channels, the app must be installed in the specific channel, and even then, management is limited.
Thanks for the explanation.
So the RSC permissions are only for standard channel.
Then I can see a usecase for ChannelMember.Read.Group
But ChannelMember.ReadWrite.Group makes no sense in that context.
Members of Standard channels cannot be written. All team members are automatically members of all standard channels. The "write" scope makes no sense.
Can you given one example what I could do with this api? I guess I can do the same thing as with only the read scope. I can read the channel membes, but what can write with this API?
- Prasad_Das-MSFT
Hi jrennefeld , according to latest update from engineering team, "RSC support for shared channels has been rolled out to public preview. RSC support for private channels will be in public preview in Jan 2026."