Skip to content

update SSO verbiage #5167

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.

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

Merged
merged 2 commits into from
Apr 11, 2023
Merged
Changes from all commits
Commits
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
11 changes: 7 additions & 4 deletions docs/guides/cloud/organizations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -336,11 +336,14 @@ addition to the documentation below, refer to the Microsoft Guides for
🎉 Your integration is now complete! You can invite all of the users in your
organization to sign in through your SSO provider.

#### **Notes**
#### Notes

- Once SSO is set up in Cypress Cloud, Users should be invited via your SSO
provider, not Cypress Cloud.
- Once SSO is successfully set up, users will need to be invited via your SSO
provider, as the Cypress Cloud invitation option will be disabled.
- All SSO Users are initially added with the
[User Role](https://on.cypress.io/users#User-roles) of Member. If a User needs
[User Role](/guides/cloud/users#User-roles) of Member. If a User needs
different User Role permissions, this can be changed via Cypress Cloud by a
current member with the role of Owner or Admin.
- SSO users are separate accounts from Google/GitHub or email/password users. If
there are duplicate users, duplicates can be removed by any
[Owner or Admin](/guides/cloud/users#User-roles).