> For the complete documentation index, see [llms.txt](https://docs.diracinc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diracinc.com/general/security.md).

# Security

This will cover security features including single sign-on with identity providers.

## Single Sign-On (SSO)

BuildOS supports enterprise Single Sign-On (SSO), allowing your team to authenticate using existing corporate credentials instead of a BuildOS password.

### Supported Identity Providers

* Okta
* Microsoft Entra ID (formerly Azure AD)
* OIDC (any OpenID Connect-compatible provider)

### Logging in with SSO

When SSO is enabled for your team, the login flow changes to use your identity provider:

1. Go to the BuildOS login page and enter your email address.
2. BuildOS detects your team's configured SSO provider.
3. Instead of a password field, you will see a **Login with \[Provider]** button showing your provider's logo (Okta or Microsoft).
4. Click the button. A popup window opens to your identity provider's login page.
5. Authenticate with your corporate credentials.
6. The popup closes and you are logged into BuildOS.

{% hint style="info" %}
If your team requires SSO, you will not be able to log in with a BuildOS password. All authentication is handled through your identity provider.
{% endhint %}

### Multi-Factor Authentication

When SSO is required for your team, MFA is managed by your SSO provider. Any MFA policies configured in Okta or Entra ID apply automatically during the SSO login flow — there is no separate MFA configuration in BuildOS.

### Configuration

SSO is configured at the team level by an administrator. Contact your BuildOS account representative to set up SSO for your team. You will need to provide:

* Your identity provider type (Okta, Microsoft Entra ID, or OIDC)
* Your provider's client configuration details