From 0ca469b315183d83503c1cb8ea86dccf5935dbdf Mon Sep 17 00:00:00 2001 From: Muhammad-Sharif Moustafa Date: Mon, 12 Jan 2026 21:41:51 -0500 Subject: [PATCH] Add SSO setup caution for collaborators --- docs/projects/sso.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/docs/projects/sso.md b/docs/projects/sso.md index 4fd108324..9688d63cf 100644 --- a/docs/projects/sso.md +++ b/docs/projects/sso.md @@ -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 @@ -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. @@ -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. \ No newline at end of file +Yes. Collaborator access is managed per project, so role mappings must be set up individually for each project.