> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/system-management/settings/single-sign-on-sso.md).
# Single sign-on (SSO)
Single sign on (SSO) enables DoControl users in your organization to login with a secure set of user credentials that meet identity governance and security requirements. You can also enforce SSO to ensure:
* **Robust security** - With SSO, there is no need for user names, passwords, or password rotation. Centralized authentication through a single identity provider (IdP) reduces the attack surface compared to multiple separate logins.
* **Better access control and governance** - Admin users can enforce policies, session timeouts, and conditional access rules consistently.
* **Improved compliance** - SSO simplifies tracking who accessed what and when, facilitating compliance with standards such as ISO 27001, SOC 2, and GDPR.
{% hint style="warning" %}
* You need **Admin** permission to integrate DoControl with SSO.
* After you define your SSO connection, you can [enforce](/docontrol-user-guide/system-management/settings/single-sign-on-sso/enforce-sso-login.md) single sign-on for DoControl.
{% endhint %}
You can integrate DoControl with the following identity providers to enable single sign-on.
{% hint style="success" %}
Except for Google and Okta, you need to add a [generic SAML](/docontrol-user-guide/system-management/settings/single-sign-on-sso/generic-saml.md) connection when connecting your identity provider to DoControl.
{% 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://docs.docontrol.io/docontrol-user-guide/system-management/settings/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.