> 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/settings/integrations/authentication.md). # Authentication Swarmia supports authentication with GitHub, Google, Microsoft, and Okta. When signing up, you select either GitHub, [Google](/settings/integrations/authentication/google-single-sign-on.md), or [Microsoft](/settings/integrations/authentication/microsoft-entra-id-single-sign-on.md) as the initial authentication method for your Swarmia organization. Once the signup is complete, it's possible to switch the authentication method to any of the three or configure [Okta](/settings/integrations/authentication/okta-single-sign-on.md). If you use GitHub to authenticate, all members of the connected GitHub organization can access Swarmia. If you have connected multiple GitHub organizations, you can control whether users need to be members in all or any of the organizations to access Swarmia. All users will be able to view metadata (e.g., pull request names) from integrated repositories. Use caution with sensitive repositories. When installing the app, it's possible to manually choose GitHub repositories you want to connect to Swarmia. --- # 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://help.swarmia.com/settings/integrations/authentication.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.