> For the complete documentation index, see [llms.txt](https://docs.noros.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noros.ai/getting-started/security/single-sign-on-sso.md). # Single Sign-On (SSO) Noros supports Single Sign-On so your team can sign in using your existing identity provider, simplifying access management and improving security. ### Supported Providers Noros currently supports SSO through: * **Google** — Sign in with your Google Workspace account * **Microsoft** — Sign in with your Microsoft / Azure AD account * **GitHub** — Sign in with your GitHub account ### Signing In with SSO 1. Visit [noros.ai](https://noros.ai) and click **Get Started** or **Sign In**. 2. Select your SSO provider (Google, Microsoft, or GitHub). 3. Authenticate with your provider's credentials. 4. You'll be signed in to Noros automatically. Noros requires a work email address — public email providers (Gmail, Yahoo, Hotmail, etc.) are not supported. Team members with matching email domains will automatically be associated with your organization's Noros account. ### Coming Soon Support for additional identity providers is planned: * **Okta** * **Auth0** ### Need a Different Provider? If your organization requires SSO through a provider not listed above, contact to discuss your requirements. We're actively expanding our SSO integrations. --- # 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.noros.ai/getting-started/security/single-sign-on-sso.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.