> 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/administration/vertical-management/rbac-operational-workflow/login-to-avo-assure-with-okta.md).
# Login to Avo Assure with OKTA
### SSO (Single Sign-On)
SSO simplifies user authentication across multiple systems, and RBAC ensures users can only access resources appropriate to their roles. Together, they provide secure and efficient access management.
### Steps to Login
1. On **Login** page, Select **Use Single Sign-On/SAML**.
2. On **Login with SSO/SAML** page, in **User ID** textbox, enter your organization's user id.
1. Select **Submit**, Connecting to Avo Assure page appears.
2. In **Password** textbox, enter password for your organization's user id.
{% hint style="info" %}
Note:
* You can also select **Keep me signed in** checkbox to keep your account logged in.
* The system asks for a password only when you log in for the first time.
{% endhint %}
5. Once the credentials are entered, select **Sign in**. The Avo Assure **Home** page appears.
---
# 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/administration/vertical-management/rbac-operational-workflow/login-to-avo-assure-with-okta.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.
