> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/account/performance-and-security/how-to-set-up-the-sso.md).
# How to set-up the SSO
For security reasons, your company may choose to use **single sign-on (SSO)**. This is a unique authentication system that enables you to connect to several platforms using the same email address and password.
AB Tasty lets you implement SSO through **SAML 2.0**, an open-standard data format for exchanging authentication and authorization information. AB Tasty’s SSO feature allows you to secure your workspace and control your users’ access. All your team members can log in to AB Tasty using one set of sign-in credentials from existing authentication providers. SSO is an email-level feature that will apply across all projects and experiments.
When you use SSO, our platform automatically links AB Tasty to your professional portal.
### Before you begin
* You must have Super Admin or Admin rights to access SSO settings.
* Make sure your Identity Providers can communicate with AB Tasty – some Identity Providers are limited to internal communication, which blocks the use of SSO with AB Tasty
* AB Tasty only manages SP-initiated SSO, so please ensure your Identity Provider is compatible
## Set-up your SSO
{% stepper %}
{% step %}
### Access the SSO configuration page
1. In the upper right corner of AB Tasty, go to **Settings**.
2. Select **Organization**.
3. Click **Single Sign-On**.
{% endstep %}
{% step %}
### Configure your SSO
1. Click **Configure SSO.**
2. Review the automatically generated **ACS URL** and **Entity ID**.
3. In a separate window, log in your identity provider platform and generate your Identity Provider (IdP) metadata file (XML format).
* If your provider is Okta, please read our article dedicated to [Okta SAML integration](broken://pages/whBDvoNGDg6Ci1GzIgbj)
* If your provider is Microsoft, please read our article dedicated to[ Microsoft Entra ID SAML integration](broken://pages/oQR4vul4TslPEFp8te45)
4. Upload your IdP metadata XML file in AB Tasty SSO configuration module.
5. Click **Save**.
[The SSO page displays **Email Domains** and **Activation** sections ](#user-content-fn-1)[^1]
{% endstep %}
{% step %}
### Manage email domains
1. In the SSO configuration page, go to **Email Domains** section.
2. Click **Add Domain** and enter the domain (e.g., company.com).
3. To remove a domain, click the trash icon next to the domain.
{% hint style="info" %}
You cannot remove the last domain if SSO is active.
{% endhint %}
{% endstep %}
{% step %}
### Activate your SSO
1. On the Activation section, toggle on the SSO.
2. Choose the authorized login method for your organization.
{% hint style="info" %}
Once **SSO only** login is enabled on your account, the ability to log in with an email password will be disabled, meaning that you can no longer log in to your AB Tasty account by manually entering your password.
{% endhint %}
Your SSO provider is added and pending activation.
{% endstep %}
{% endstepper %}
## Activate or deactivate SSO
* [x] In the SSO configuration page, in the **Activation** section, toggle the **Enable** **SSO for your organisation** switch.
## Troubleshooting
* If you encounter errors during setup, verify your IdP metadata file.
* Ensure all allowed domains are correct and match your users’ email addresses.
* For further help, contact your internal IT team.
* For more information on our SSO system, please read[ our dedicated FAQ](/help-center/faq/faq-about-sso.md)
[^1]: 
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.abtasty.com/account/performance-and-security/how-to-set-up-the-sso.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.