> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/getting-started/creating-an-account/single-sign-on-sso.md).

# Single sign-on (SSO)

SSO is available only to members of an Enterprise group that has been invited to take part in the early access test. If SSO is turned on for your account, you must use it to log in.

## Creating an account that uses SSO

If an enterprise group Owner arranged for your account to be created and connected to their Enterprise group, you may be able to use SSO to log in immediately. If you intend to join a group that has SSO turned on, complete the following steps:

1. Follow the steps in either [Creating an account in the web manager](/engage/getting-started/creating-an-account/creating-an-account-in-the-web-manager.md) or [Creating an account in the ENGAGE app](/engage/getting-started/creating-an-account/creating-an-account-in-the-engage-app.md) to create an account and verify your email address. You will initially need to create a password for your account.
2. Ask the group owner or an administrator to invite you to the group, and then accept the invitation. For more information, see [Managing your group membership](/engage/web-manager/managing-your-group-membership.md).

You can then use SSO to log in. See the following section for more information.

## Using SSO to log in

To use SSO to log in to either the ENGAGE application or the web manager, complete the following steps:

1. On the log-in screen, select **Log in with SSO**.
2. On the **Log in with SSO** page, enter your username or email address, and then select **Continue**.
3. Complete the steps required by your authentication provider to log in to your account.

<figure><img src="https://3460182399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwVx6bvwqEE7tD0TYOcfj%2Fuploads%2Fgit-blob-cafc62c938347f35ed11dd60798efc2c35b521da%2Fsso_log_in_app.png?alt=media" alt=""><figcaption><p>Option to log in with SSO in the ENGAGE application</p></figcaption></figure>

<figure><img src="https://3460182399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwVx6bvwqEE7tD0TYOcfj%2Fuploads%2Fgit-blob-72579e1af29492a3088efcb4d6f0161430a576e9%2Fsso_log_in_web.jpg?alt=media" alt=""><figcaption><p>Option to log in with SSO in the web manager</p></figcaption></figure>


---

# 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.engagevr.io/engage/getting-started/creating-an-account/single-sign-on-sso.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.