> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/structural-user-access/account-creation-and-authentication/user-authentication.md). # Structural user authentication How you authenticate into Structural is based on: * Whether your organization enabled single sign-on (SSO) for authentication. * Whether your organization requires SSO for authentication. * How you created your account: * Provided an email address and created a Structural password. * On Cloud only, used the Google signup option. This option is not available after an organization enables SSO. * Used the SSO signup option. ## Structural Cloud organization On Structural Cloud, on the login page, to start the authentication: 1. In the **Email Address** field, provide your email address. 2. Click **Continue**. ### SSO not enabled On the next page, if you used the Google signup option, then click **Log in using Google**. You then authenticate through Google. If you signed up with an email address and Structural password: 1. In the **Password** field, provide your Structural password. 2. Click **Submit**. ### SSO enabled but not required When SSO is enabled but not required, then authentication works as follows, based on how you created your account. #### SSO signup If you signed up with SSO, then you always authenticate with SSO. After you provide the email address: 1. Click **Log in using \**. 2. Authenticate through the SSO provider. #### Google signup After SSO is enabled, you must authenticate with SSO. If the email address for SSO is the same as the one that you used to create the account, then Structural preserves your account workspaces and permissions. #### Email address and password signup If you signed up with an email address and password, then you can either: * Authenticate with SSO. * Authenticate with your password. However, once you authenticate with SSO, you must always authenticate with SSO. You can no longer use your Structural password. If the email address for SSO is the same as the one that you used to create the account, then Structural preserves your account workspaces and permissions. ### SSO required When SSO is required, then you must authenticate with SSO. You cannot use a Structural password. If you did not sign up with SSO, but your email address for SSO is the same as the one that you used to create the account, then Structural preserves your account workspaces and permissions. ## Self-hosted instance ### SSO not enabled When SSO is not enabled, then on the login page: 1. In the **Email Address** field, provide your email address. 2. In the **Password** field, provide your Structural password. 3. Click **Log In**. ### SSO enabled but not required When SSO is enabled but not required, then authentication works as follows, based on how you created your account. #### SSO signup If you signed up with SSO, then you always authenticate with SSO. On the login panel: 1. Click **Log in using \**. 2. Authenticate through the SSO provider. #### Email address and password signup If you signed up with an email address and password, you can either: * Authenticate with SSO. * Authenticate with your password. However, once you authenticate with SSO, you must always authenticate with SSO. You can no longer use your Structural password. If your email address for SSO is the same as the one that you used to create the account, then Structural preserves your account workspaces and permissions. Note that if you do not require SSO, you can maintain an administrator account that uses a standard email address and Structural password. If there is an issue with the SSO configuration, then that administrator can still log in to Structural. ### SSO required When SSO is required, then you always authenticate with SSO, regardless of how you created your account. If you did not sign up with SSO, but your email address for SSO is the same as the one that you used to create the account, then Structural preserves your account workspaces and permissions. ### Note on SSO group membership On self-hosted instances that have a [filter for SSO groups](/app/structural-user-access/single-sign-on/sso-limit-groups.md), SSO group membership is based on the most recent group configuration from the SSO provider. You inherit the permissions that are granted to the groups that you are currently a member of, in addition to the permissions that are granted directly to your account. --- # 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.tonic.ai/app/structural-user-access/account-creation-and-authentication/user-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.