Skip to content

Add caution about collaborator removal during SSO setup #1321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mshmoustafa wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add caution about collaborator removal during SSO setup #1321

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions docs/projects/sso.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,10 @@ In the RevenueCat dashboard:

![Collaborators](/docs_images/projects/sso-collaborators.png)

:::caution
Enabling SSO **removes all existing project collaborators** and replaces them with SSO group mappings. Make sure the **project owner** completes setup in RevenueCat **and** in your identity provider before activating SSO.
:::

2. Add an **SSO Group**
3. Select the **RevenueCat role** that group should receive

Expand All @@ -68,11 +72,11 @@ Changes may take a few minutes to sync.

**Role precedence (highest wins):**

1. Admin
2. Developer
3. Growth
4. Support
5. View Only
1. Admin
2. Developer
3. Growth
4. Support
5. View Only

> Mapping SSO groups updates project collaborators and may affect currently signed-in users.

Expand Down Expand Up @@ -100,4 +104,4 @@ The user is granted the **highest** applicable role based on role precedence.

### Do I need to configure SSO group mappings for each project?

Yes. Collaborator access is managed per project, so role mappings must be set up individually for each project.
Yes. Collaborator access is managed per project, so role mappings must be set up individually for each project.