> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/organizations-and-projects/create-an-organization.md).

# Create an Organization

{% columns %}
{% column %}
**What is covered**

* Create a new Organization
* Name it for fast searching
* Confirm access settings (if prompted)
  {% endcolumn %}

{% column %}
**At a glance**

* **Time:** \~2–5 minutes
* **Access:** Account Admin (or equivalent)
  {% endcolumn %}
  {% endcolumns %}

### Overview

Organizations separate work by client, department, or business unit. They provide a boundary for access control and reporting.

### Key Concepts

* **Organization**: container for Projects
* **Organization scope access**: shared access across multiple Projects
* **Segmentation**: Segment Types and Segments are managed at Organization scope

### How It’s Used

Most Accounts use one Organization per client or department. Projects are created inside the Organization for each initiative.

### Benefits

* Prevents cross-client or cross-department mixing
* Simplifies access control for multi-Project teams
* Improves reporting consistency within an Organization

<figure><img src="/files/7PTFEgXscCw5xgwkwarM" alt=""><figcaption></figcaption></figure>

### Setup Steps

{% stepper %}
{% step %}

### Open Organizations

Open the **Organizations** page from the main navigation.

<figure><img src="/files/XYcRmWzfEYILxjZUohfs" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Create an Organization

Click **New organization** (or **Add organization**).

<figure><img src="/files/1Rz4t6VVS4Pdl5HOeYKk" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Enter details

Set:

* **Name** (for example: `ACME Corp`)
* **Description** (optional, one sentence)
* **Visibility / access** (if shown)

{% endstep %}

{% step %}

### Submit

Create the Organization.

<figure><img src="/files/tsmtLzFnwbgSeK4wmUzs" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/MYwkC25hrljBpkc9hURu" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

#### Prerequisites

* Sign-in is working.
* Permission exists to create Organizations.
* Organization name is available.

{% hint style="warning" %}
If the option to create an Organization is not available, request access from an Account Admin.
{% endhint %}

### Best Practices

Keep names stable and searchable.

Good patterns:

* `Client — Program` (consulting)
* `Department` (enterprise)

Operational guidance:

* Create Organizations early to simplify access control.
* Keep naming consistent and avoid internal abbreviations.
* Add Teammates after creation and use least-privilege roles.

#### Troubleshooting

<details>

<summary>Organization creation is not available</summary>

This is usually a permissions issue. Account Admin access (or equivalent) is often required.

Ask an Account Admin to grant access or create the Organization.

</details>

### Summary

Next steps:

* [Create a Project](/getting-started/create-a-project.md)
* [Add Teammates](/organizations-and-projects/add-teammates.md)
* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/organizations-and-projects/create-an-organization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.