> For the complete documentation index, see [llms.txt](https://docs.navless.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navless.ai/security/sso-single-sign-on.md).

# SSO (Single Sign-on)

To get started, please reach out to your sales contact or support for enabling SSO in your account (this is a paid add-on). We will share the secure link through which you can pick your provider.

Our support team will share the secure link through which you can pick the provider to configure for your account. Once the steps are complete, then SSO will be turned on for your account users.

## How to Log in to Navless Using SSO

If your organization uses Single Sign-On (SSO), you can log in to Navless seamlessly. Follow the steps below to get started:

### Step 1: Get Invited to Navless

A Navless account admin from your organization must invite you to join Navless. You'll receive an email invitation once this step is completed.

Note: Depending on your organization's SSO configuration, your IT team may also need to add you to the SSO system before you can log in.

#### Step 2: Accept Your Navless Invitation

Once invited, you’ll receive an email with a link to create your account.

1. Open the invitation email from Navless.
2. Click the provided link to accept the invitation.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXdl1MXhNDSqF-ZKtfci6QWsiY5PQHmMdctA_Fq1AhqhuxUQQLX6dC7q0cQMdALP97IJIO3Si9FwBy6Kqni1KBlOb5nKtVz06qiDdq7AehYsJ5LHQiE9_gEL0s71wo_DjmnhBnFAAw?key=hnE6joktFmYdTLh7S8G06SFw)

3. Follow the on-screen instructions to complete your account setup.

#### Step 3: Log in with SSO

Once your account is set up, you can log in to Navless using SSO:

1. Go to[ Navless's login page](https://app.navless.ai/).
2. Enter your company email address (if prompted).
3. Authenticate through your organization’s SSO system.

You’re now logged in and ready to use Navless!

If you experience any issues, contact your internal IT team or reach out to Navless Support.

## SSO Providers

Below is a list of providers supported. Click to learn more about the configuration steps.

* [Okta SAML](https://workos.com/docs/integrations/okta-saml)
* [OneLogin SAML](https://workos.com/docs/integrations/onelogin-saml)
* [Auth0](https://workos.com/docs/integrations/auth0-saml)
* [Azure AD ](https://workos.com/docs/integrations/azure-ad-saml)[SAML](https://workos.com/docs/integrations/azure-ad-saml)
* [Google OAuth](https://workos.com/docs/integrations/g-suite-oauth)
* [Google SAML](https://workos.com/docs/integrations/google-saml)
* [Microsoft AD FS SAML](https://workos.com/docs/integrations/microsoft-ad-fs-saml)
* [ADP Open ID Connect](https://workos.com/docs/integrations/adp-oidc)
* [OpenID Connect](https://workos.com/docs/integrations/oidc)
* [CAS SAML](https://workos.com/docs/integrations/cas-saml)
* [ClassLink](https://workos.com/docs/integrations/classlink-saml)
* [Cloudflare](https://workos.com/docs/integrations/cloudflare-saml)
* [CyberArk SAML](https://workos.com/docs/integrations/cyberark-saml)
* [Duo](https://workos.com/docs/integrations/duo-saml)
* [SAML](https://workos.com/docs/integrations/generic-saml)
* [JumpCloud SAML](https://workos.com/docs/integrations/jumpcloud-saml)
* [Keycloak](https://workos.com/docs/integrations/keycloak-saml)
* [Microsoft OAuth](https://workos.com/docs/integrations/microsoft-oauth)
* [miniOrange](https://workos.com/docs/integrations/mini-orange-saml)
* [Oracle SAML](https://workos.com/docs/integrations/oracle-saml)
* [PingFederate SAML](https://workos.com/docs/integrations/ping-federate-saml)
* [PingOne SAML](https://workos.com/docs/integrations/ping-one-saml)
* [Salesforce](https://workos.com/docs/integrations/salesforce-saml)
* [Simple php SAML](https://workos.com/docs/integrations/simple-saml-php-saml)
* [VMWare](https://workos.com/docs/integrations/vmware-saml)


---

# 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.navless.ai/security/sso-single-sign-on.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.
