Clarify that SCIM group membership provisions users into secondary accounts#3229
Open
ably-sync-bot wants to merge 1 commit intomainfrom
Open
Clarify that SCIM group membership provisions users into secondary accounts#3229ably-sync-bot wants to merge 1 commit intomainfrom
ably-sync-bot wants to merge 1 commit intomainfrom
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The current docs only mention that new SCIM users are provisioned into the default account with a Developer role. They don't explain that linking a SCIM group to a secondary account also provisions user accounts for group members in that account.
The Group Roles section only talks about role inheritance, which implies the user already exists in the account — but the group-account linking is what actually creates the user in that account.
Changes
Context
This came up during a support investigation. The docs gap made it harder to diagnose because it wasn't clear whether group membership was supposed to provision users into secondary accounts or just assign roles.
Submitted by: Mike Clark (mike.clark@ably.com)
Submitted at: 2026-02-27T11:36:11.982Z
Created via
githubCreatePRWithFileMCP tool