> For the complete documentation index, see [llms.txt](https://docs.the-cloud-storage-guide.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.the-cloud-storage-guide.io/cloud-storage-platforms/egnyte-overview/users-and-groups/sso-integrations.md).

# SSO Integrations

Egnyte can integrate with all major SSO providers

Egnyte is able to integrate with any SSO identity provider using SAML 2.0.  Support is built-in for all major SSO providers, and other vendors using SAML 2.0 can be added by contacting Egnyte Support. 

### Enabling an SSO Integration

To enable SSO, the Egnyte Account must have the External Authentication add-on. Enabling SSO is done through the Admin Panel under Security & Authentication in Configuration. 

Select the type of SSO "Such as SAML 2.0", choose the identity provider, and fill out the required fields. Certain providers such as Azure AD, will require the creation of an application for SSO. 

See Egnyte's [SSO integration page](https://helpdesk.egnyte.com/hc/en-us/articles/201638954-Single-Sign-On-SSO-Configuration) for links on how to set up SSO for specific providers. 

### Google SSO

The process for Google SSO differs from other identity providers. Simply change the sign-on authentication to Google Apps within Egnyte, and any Google account with an email that corresponds to an Egnyte user can sign in to Egnyte using Google. 


---

# 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.the-cloud-storage-guide.io/cloud-storage-platforms/egnyte-overview/users-and-groups/sso-integrations.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.