> 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-access-new-account.md).

# Creating a new account in an existing organization

The available options to add an account to an existing organization are based on:

* Whether single sign-on (SSO) is enabled.
* If SSO is enabled, whether it is also required.
* On self-hosted instances, whether users are permitted to create accounts.

## Structural Cloud organization

To be added to an existing Cloud organization, a new account email address must either:

* Use a domain that is listed in the domains for an organization's Structural license.
* Have an invitation to join an organization.

Free trial accounts always start a new organization, regardless of the email address domain.

For more information, go to [Structural organizations](https://docs.tonic.ai/app/structural-user-access/structural-organizations.md#when-is-a-new-user-added-to-an-existing-organization)

### SSO not enabled <a href="#cloud-no-sso" id="cloud-no-sso"></a>

When SSO is not enabled, then to create an account:

1. On the login page, click **Create Account**.
2. On the account creation panel, either:
   * Use the Google sign-up option (**Create account using Google**). Provide the Google email address to use for the account, then authenticate through Google.
   * Provide an email address, create a Structural password, then click **Create Account**.

### SSO enabled but not required <a href="#cloud-sso-enabled" id="cloud-sso-enabled"></a>

When SSO is enabled but not required, you can use either:

* SSO option
* Email address and password option

You cannot use the Google signup option.

#### SSO option <a href="#cloud-sso-enabled-sso" id="cloud-sso-enabled-sso"></a>

To use the SSO option:

1. On the login page, enter your email address, then click **Continue**.
2. On the login panel, click **Log in using \<SSO provider>**.
3. Provide your email address.
4. Authenticate through the SSO provider.

#### Email address and password option <a href="#cloud-sso-enabled-email" id="cloud-sso-enabled-email"></a>

To use the email address and password option:

1. On the login page, click **Create Account**.
2. On the account creation panel, provide an email address.
3. Create a Structural password.
4. Click **Create Account**.

### SSO enabled and required <a href="#cloud-sso-required" id="cloud-sso-required"></a>

When SSO is both enabled and required, then to create an account, you must use the SSO option.

1. On the login page, enter your email address, then click **Continue**.
2. On the login panel, click **Log in using \<SSO provider>**.
3. Provide your email address.
4. Authenticate through the SSO provider.

## Self-hosted instance

### Whether account creation is permitted <a href="#self-account-creation-setting" id="self-account-creation-setting"></a>

On a self-hosted instance, users can only create an account when the [environment setting](https://docs.tonic.ai/app/admin/environment-variables-setting.md) `TONIC_DISABLE_ACCOUNT_CREATION` is set to `false`. This is the default value.

When the setting is `true`, then users cannot create a Structural account, even if SSO is enabled.

You can configure this setting from the **Environment Settings** tab on **Structural Settings**. So for example, you can set it to `false` only when a user needs to create an account, then set it to `true` to prevent account creation.

To get started, on the login page, click **Create Account**.

### SSO not enabled <a href="#self-no-sso" id="self-no-sso"></a>

When SSO is not enabled, then to create an account, on the account creation panel:

1. Provide an email address.
2. Create a Structural password.
3. Click **Create Account**.

### SSO enabled but not required <a href="#self-sso-enabled" id="self-sso-enabled"></a>

When SSO is enabled but not required, then to create an account, you can use either the SSO option or the email address and password option.

#### SSO option <a href="#self-sso-enabled-sso" id="self-sso-enabled-sso"></a>

On the account creation page:

1. Click **Create account using \<SSO provider>**.
2. Provide your email address.
3. Authenticate through the SSO provider.

#### Email address and password <a href="#self-sso-enabled-email" id="self-sso-enabled-email"></a>

On the account creation page:

1. Provide your email address.
2. Create a Structural password.
3. Click **Create Account**.

### SSO enabled and required <a href="#self-sso-required" id="self-sso-required"></a>

When SSO is both enabled and required, then to create an account, you must use the SSO option.

On the account creation page:

1. Click **Create account using \<SSO provider>**.
2. Provide your email address.
3. Authenticate through the SSO provider.


---

# 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-access-new-account.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 `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.
