Skip to content

Commit 1fc680e

Browse files
committed
moving info to FAQs
1 parent f3cc445 commit 1fc680e

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

src/segment-app/iam/sso.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -101,17 +101,11 @@ Enter your domain and click "Add Domain." When you click verify, you're given tw
101101
## Configuring SSO to access multiple workspaces
102102
To configure SSO for multiple workspaces, your admin must configure access to each workspace as a separate app in your identity provider. You are unable to use verified domain(s) across multiple workspaces and will encounter the following error if you add a domain that is already verified in another workspace:
103103

104-
105104
> warning ""
106105
> **Warning**: This domain has already been claimed.
107106
108107
Once your admin has configured separate apps for each workspace in your IdP, the end-users can log in to the IdP and click on the relevant app for the workspace you are trying to access. This is also referred to as IdP-initiated SSO.
109108

110-
> info "Swithcing between Segment workspaces"
111-
> Becasue a user, who logged in via SSO, is only signed in for one Segment workspace, the user needs to sign in again to access another workspace.
112-
113-
In this case, when the end-users visit [Segment login page](https://app.segment.com/login){:target="_blank"} to sign in via SSO, the users will only be redirected to one workspace which is also linked with the verified domain(s) because the login page only supports [Segment-initiated SSO](/docs/segment-app/iam/sso/#enabling-segment-initiated-login).
114-
115109
## Okta setup
116110

117111
The Okta/Segment SAML integration supports the following features:
@@ -179,7 +173,10 @@ Segment allows users to own their own workspaces. While your IdP authentication
179173
Workspace owners can invite additional owners with any domain using the traditional invite mechanism. If the workspace is configured to require SSO, and the user is not on your IdP, you can add an Exemption under **Workspace Settings > Authentication > Advanced Settings**.
180174
{% endfaqitem %}
181175

182-
{% faqitem How do I configure SSO to access multiple workspaces? %}
183-
To use SSO for multiple workspaces, your admin must configure access to each workspace as a separate app in your identity provider.
176+
{% faqitem What happens after I configured SSO to access multiple workspaces? %}
177+
After SSO is configued to access multiple workspaces, you will have slightly different signin experience in the below scenarios
178+
1. When you are switching between workspaces, and you have already logged in via SSO, you will need to sign in again before accessing other workspaces.
179+
2. When you visit [Segment login page](https://app.segment.com/login){:target="_blank"} to sign in via SSO, you will only be redirected to one workspace which is also linked with the verified domain(s). It is because you are actually using the [Segment-initiated SSO](/docs/segment-app/iam/sso/#enabling-segment-initiated-login) in this scenario.
180+
184181
{% endfaqitem %}
185182
{% endfaq %}

0 commit comments

Comments
 (0)