> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/support-resources/troubleshooting-guides/generic/sso-login-problems.md).

# SSO Login Problems

<table><thead><tr><th width="214.33331298828125">Problem</th><th width="208.3333740234375" valign="middle">Cause</th><th>Instructions to Resolve</th></tr></thead><tbody><tr><td>SSO login fails, redirects you to the login page repeatedly, displays an error on your company's sign-in page, or allows you to log in but does not display any projects.</td><td valign="middle">The issue may be related to missing user account details, role or project mapping, or your company's identity provider configuration.</td><td><p></p><ul><li>If SSO login fails or redirects you to the login page, contact your Admin to verify your user account, role, and project mapping in Avo Assure.</li><li>If an error appears on your company's sign-in page, contact your IT team to check the identity provider configuration.</li><li>If you can log in but cannot see any projects, ask your Admin to map your user account to a project. For more information, see <a href="https://docs.avoautomation.com/avo-assure/administration/vertical-management/rbac-operational-workflow/project-management-in-vertical/project-mapping-in-vertical.md">Project Mapping in Vertical</a>.</li></ul></td></tr></tbody></table>


---

# 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.avoautomation.com/avo-assure/support-resources/troubleshooting-guides/generic/sso-login-problems.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.
