> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/sso-setup-guide/manage-users-with-sso.md).

# Manage Users with SSO

Manage how Enterprise **SSO** affects the way users are authenticated and managed within your **Rillet** organization, since it handles authentication only and does not automatically provision users. Before a team member can log in using SSO, invite them first by following the [**Manage Members**](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/user-roles-and-permissions-overview/manage-members.md) guide, since user management afterward depends on whether that user's email domain is verified.

### Manage Users with Non-Verified Domains

When inviting a user whose email domain does not match any verified SSO domains (for example, an external consultant or auditor), you can choose their authentication method:

| Method         | How It Works                                                                 |
| -------------- | ---------------------------------------------------------------------------- |
| Standard       | Magic link, OTP, or OAuth.                                                   |
| Enterprise SSO | Authenticates through your identity provider, same as verified-domain users. |

You can switch a user's authentication method between **Enterprise SSO** and **Standard** at any time from the member's settings.

### Manage Users with Verified Domains

If a user's email domain matches one of your verified organization domains, **Enterprise SSO** is automatically assigned as their only authentication method. This cannot be changed: all users on verified domains must authenticate through your identity provider, and other login methods (magic link, one-time password, Google or Microsoft OAuth) are not available for these users.

### Understand How Users Log In with SSO

Once a user has been invited to your Rillet organization, review how the SSO login flow works:

| Stage        | What Happens                                                                                             |
| ------------ | -------------------------------------------------------------------------------------------------------- |
| Enter email  | The user enters their email address on the Rillet login page.                                            |
| Redirect     | Rillet detects that SSO is enabled for the email domain and redirects the user to the identity provider. |
| Authenticate | The user authenticates using the identity provider (credentials, MFA, and other methods).                |

After successful authentication, the user is redirected back to Rillet and logged in automatically.

### See Also

To learn more about SSO setup and related configuration in **Rillet**, review these articles:

* [**SSO Setup Guide**](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/sso-setup-guide.md)
* [**Manage Members**](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/user-roles-and-permissions-overview/manage-members.md)
* [**Manage Access and Roles**](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/user-roles-and-permissions-overview/manage-access-and-roles.md)
* [**Custom Fields**](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/custom-fields.md)
* [**Fields Overview**](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/custom-fields/fields-overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/sso-setup-guide/manage-users-with-sso.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
