> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/resources/security-and-data-retention/single-sign-on-sso-saml.md).

# Single Sign-On (SSO) / SAML

Many organizations use tools like Okta, Active Directory, or Google Workspace to manage users. Swarmia supports Single Sign-On through Okta, Microsoft Entra ID, Google and secure login through GitHub.

To enable Single Sign-On for your organization, follow these [instructions](/settings/integrations/authentication.md).

If your organization isn't using Single Sign-On providers, you can log in to the product using GitHub login. This allows us to avoid security hurdles with self-managed passwords and use an identity provider that your organization already trusts.

The typical Single Sign-On features work through the GitHub authentication:

1. You'll be able to get access to Swarmia when you have access to the relevant GitHub organization, so you don't need to create Swarmia user accounts for each employee.
2. When an account is disabled from your SSO provider, if you've configured it to be deleted from GitHub, the change will also propagate to Swarmia automatically.

**Please note that enabling Single Sign-On through Okta disables the GitHub login method for all users.**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.swarmia.com/resources/security-and-data-retention/single-sign-on-sso-saml.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 `build a script that syncs our docs to a CMS` 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.