> 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/google-single-sign-on/frequently-asked-questions.md). # Frequently asked questions ### How can I disable Google authentication? If you wish to disable Google authentication and revert to GitHub-initiated login, contact support at . ### **What happens if my organization has Google enabled and someone logs in with their GitHub account?** Swarmia detects that the user belongs to your Github organization and the user gets redirected to the Google login page. ### **What happens to existing users and teams if I enable Google authentication?** You will have the same users and teams. People will be prompted to link their GitHub account to their Google credentials when they log in the next time. ### **What happens if I have multiple Swarmia organizations** You can use Google authentication with all your Swarmia organizations. Upon authentication you will be prompted to select the organization you want to log into. ### **I need to allow other domains to log in to our instance with Google** Please contact us to our support at and we can include any additional domains to your installation --- # 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/google-single-sign-on/frequently-asked-questions.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.