Skip to content

Commit 0ca469b

Browse files
committed
Add SSO setup caution for collaborators
1 parent fe04a73 commit 0ca469b

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

docs/projects/sso.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,10 @@ In the RevenueCat dashboard:
5959

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

62+
:::caution
63+
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.
64+
:::
65+
6266
2. Add an **SSO Group**
6367
3. Select the **RevenueCat role** that group should receive
6468

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

6973
**Role precedence (highest wins):**
7074

71-
1. Admin
72-
2. Developer
73-
3. Growth
74-
4. Support
75-
5. View Only
75+
1. Admin
76+
2. Developer
77+
3. Growth
78+
4. Support
79+
5. View Only
7680

7781
> Mapping SSO groups updates project collaborators and may affect currently signed-in users.
7882
@@ -100,4 +104,4 @@ The user is granted the **highest** applicable role based on role precedence.
100104

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

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

0 commit comments

Comments
 (0)