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

# Single Sign On

Set up Single Sign On for your Pushly organization with Okta, Google Workspace, or Microsoft Azure AD.

Single Sign On (SSO) lets your team sign in to Pushly through your identity provider. Configure a provider once at the organization level. Users authenticate through that provider when their email domain matches an associated domain.

### Before you begin

You need:

* An administrator for your identity provider.
* Access to **Organization Settings** in Pushly.
* The email domains your team uses to sign in.

{% hint style="warning" %}
Each user must be invited to Pushly. Identity provider access does not create Pushly users or assign their roles.
{% endhint %}

### Choose your provider

{% content-ref url="/pages/oHu4O8s4pFe2coZW5X1E" %}
[Okta Workforce](/platform/organizations/single-sign-on/okta-workforce.md)
{% endcontent-ref %}

{% content-ref url="/pages/3k0gxpdJCnvPYW00cz1Y" %}
[Google Workspace](/platform/organizations/single-sign-on/google-workspace.md)
{% endcontent-ref %}

{% content-ref url="/pages/sVh9LjhkByJXWzU6X7zY" %}
[Microsoft Azure AD](/platform/organizations/single-sign-on/microsoft-azure-ad.md)
{% endcontent-ref %}

### Troubleshooting

If a user cannot sign in, verify their email matches an associated domain. Then confirm the user has both identity provider access and a Pushly invitation.


---

# 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://documentation.pushly.com/platform/organizations/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.