> For the complete documentation index, see [llms.txt](https://messagebird.gitbook.io/applications/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://messagebird.gitbook.io/applications/settings/account/organization-settings/single-sign-on-sso/enforce-single-sign-on-sso.md).
# Enforce Single-Sign On (SSO)
In order to ensure that your users can only login via SSO and not alternative login methods such as username/password and Google Login, you can enforce SSO on your organization.
{% hint style="warning" %}
Before enforcing SSO, make sure you've fully completed [Set up Single-Sign On (SSO)](/applications/settings/account/organization-settings/single-sign-on-sso/set-up-single-sign-on-sso.md), including domain validation. Enforcing SSO before your setup works can lock users out of their accounts.
{% endhint %}
1. Navigate to the Single Sign On page [here](https://app.bird.com/settings/security/access-settings) and click on Manage SSO Settings.
2. Here you can tick the Require SSO authentication toggle switch and also optionally exclude some users from enforcing SSO. This can be useful if you have misconfigured your SSO integration and can no longer login through SSO. The users specified will still be able to login with other methods and fix the settings.
Once enforced, any user who is not on the excluded list must authenticate through your configured identity provider to access the organization. Username and password, and third-party login options like Google Login, are no longer offered as login methods for the organization.
SSO can only be enforced once at least one identity provider is set up.
### Excluding users from enforcement
Excluding specific users is primarily a safety net for administrators. Consider keeping at least one organization owner excluded so that, if your SSO integration ever becomes misconfigured, someone can still access the account settings to fix it without needing to contact support.
{% hint style="info" %}
Excluded users must be members of the organization.
{% endhint %}
---
# 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://messagebird.gitbook.io/applications/settings/account/organization-settings/single-sign-on-sso/enforce-single-sign-on-sso.md?ask=&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.
.webp?alt=media)