> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/en/org/organization.md).

# Organization Management

Learn what an organization is, whether a company should create one or multiple organizations, how to create and switch organizations, and what owners are responsible for.

## What Is an Organization? <a href="#what-is-organization" id="what-is-organization"></a>

An **organization** is MaiAgent's top-level management unit, like an independently operated “digital office.” Members, roles, AI assistants, knowledge bases, plans, and Credits all belong to a specific organization, and organizations are completely isolated from one another.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-82a0780b18c6f04ac503ce0e6cb9f1a6e8aee1a2%2Forg-isolation.png?alt=media" alt="The same account can join multiple organizations, which are completely isolated from one another"><figcaption><p>The same account can join multiple organizations. Each organization has its own members, resources, plan, and owners, and cannot see the data of other organizations</p></figcaption></figure>

To learn what an organization contains and how roles and members work, see [Organization and Member Management](/maiagent-user-guide/en/org/overview.md).

***

## One Organization or Multiple Organizations? <a href="#one-or-many" id="one-or-many"></a>

For most companies, **one organization is enough**. Use roles to separate departments, assign different permissions, and control who can access assistants. You do not need to create a new organization for these purposes.

<table><thead><tr><th width="180">Scenario</th><th>Recommendation</th></tr></thead><tbody><tr><td>Departments need different permissions</td><td>Use one organization and create one role for each department</td></tr><tr><td>Employees do not want others to see the assistants they create</td><td>Use one organization and create one role per person. See the <a href="/maiagent-user-guide/en/org/roles/role-design-guide.md">Role Permission Planning Guide</a></td></tr><tr><td>Test and production environments must be separate</td><td>One organization is sufficient. The platform separates testing and production by “publishing to different roles,” so you do not need to duplicate an entire organization</td></tr><tr><td>Subsidiaries need separate billing and separate owners</td><td>Use separate organizations. Plans, Credits, and usage statistics are managed per organization</td></tr><tr><td>The two sides log in with different company accounts (SSO)</td><td>Use separate organizations. SSO settings are tied to an organization</td></tr><tr><td>Data must be completely isolated due to regulatory or contractual requirements</td><td>Use separate organizations. Nothing is shared between organizations</td></tr></tbody></table>

{% hint style="warning" %}
**The cost of using multiple organizations**

Assistants, knowledge bases, and roles cannot be shared across organizations and must be created separately in each organization. Members must also be added and maintained separately. Before creating a second organization, make sure roles truly cannot meet your needs.
{% endhint %}

***

## Create an Organization <a href="#create-organization" id="create-organization"></a>

Any account can create a new organization. The creator automatically becomes the organization's **owner**.

### 1. Open the Organization Switcher <a href="#open-switcher" id="open-switcher"></a>

Click the organization name at the top of the left menu to expand the organization list, then click <mark style="color:blue;">Create Organization</mark> at the bottom.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-be24796b02d2cd727fefeb257b7c8579055adfc1%2Forg-switcher.png?alt=media" alt="Organization switcher at the top of the left menu, with Create Organization at the bottom" width="420"><figcaption><p>The organization switcher is at the top of the left menu, with “Create Organization” at the bottom of the list</p></figcaption></figure>

### 2. Enter Organization Information <a href="#fill-in-form" id="fill-in-form"></a>

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-3e632d283a84a672737b732f46fc2fa0780f5aec%2Forg-create-dialog.png?alt=media" alt="Add Organization window" width="480"><figcaption><p>The “Add Organization” window</p></figcaption></figure>

<table><thead><tr><th width="140">Field</th><th width="90">Required</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Yes</td><td>The organization's display name on the platform. You can change it later in <a href="/maiagent-user-guide/en/org/organization-overview.md">Organization Overview</a></td></tr><tr><td>Invitation code</td><td>No</td><td>A <strong>trial invitation code</strong> provided by MaiAgent. After you paste it, the company information is filled in automatically, and you can start using the organization immediately after creation without waiting for approval</td></tr><tr><td>Company name</td><td>Yes</td><td>The company's full legal name for the approval application</td></tr><tr><td>Business registration number</td><td>No</td><td>8 digits</td></tr><tr><td>Contact phone number</td><td>Yes</td><td>Used to contact you if there are questions during the review</td></tr></tbody></table>

{% hint style="info" %}
**In simple terms:**

If you have an invitation code, paste it and the other fields will be filled in automatically. If you do not have one, enter your company information and submit it for approval. Once approved, a 14-day trial is activated. The “invitation code” on the registration page is a platform referral code and is not the same as the trial invitation code here.
{% endhint %}

### 3. Submit and Wait for Approval <a href="#submit-and-approval" id="submit-and-approval"></a>

Click <mark style="color:blue;">Confirm</mark> to submit. Applications without an invitation code are sent for review. After approval, the organization receives a 14-day trial. To continue using it during or after the trial, see [Credits Billing](/maiagent-user-guide/en/org/credits.md) or contact the sales team.

{% hint style="warning" %}
When an organization has no active plan, Organization Overview displays the data retention deadline. The data is permanently deleted when the deadline is reached, so upgrade your plan before it expires.
{% endhint %}

***

## Switch Organizations <a href="#switch-organization" id="switch-organization"></a>

After the same account joins multiple organizations, click the organization name at the top of the left menu, then select the organization you want to switch to. If there are many organizations, enter a name directly in the search box at the top. The organization you are currently in appears below the account name in the upper-right corner.

{% hint style="info" %}
After switching organizations, the assistants, knowledge bases, and conversations you see all change to those of the selected organization. If you cannot find an assistant, first check whether the correct organization is selected in the upper-left corner.
{% endhint %}

***

## Owner Responsibilities <a href="#owner-responsibilities" id="owner-responsibilities"></a>

Organization owners bypass all permission checks and have the highest level of access in the organization. An organization can have multiple owners. We recommend assigning at least two so the organization remains manageable if the sole point of contact leaves the company. Owners are responsible for the following:

<table><thead><tr><th width="200">Task</th><th>Where to do it</th></tr></thead><tbody><tr><td>View the plan expiration date and monthly usage, and change the organization name</td><td><a href="/maiagent-user-guide/en/org/organization-overview.md">Organization Overview</a></td></tr><tr><td>Customize the admin interface with the company's logos and theme color (Enterprise)</td><td><a href="/maiagent-user-guide/en/org/organization-overview.md#org-branding">Organization Overview → Organization Branding</a></td></tr><tr><td>Design roles and decide who can create assistants and who can only use them</td><td><a href="/maiagent-user-guide/en/org/roles.md">Roles and Permissions</a></td></tr><tr><td>Add members, assign roles, and remove members</td><td><a href="/maiagent-user-guide/en/org/member.md">Member Management</a></td></tr><tr><td>Log in with company accounts and synchronize the member list</td><td><a href="/maiagent-user-guide/en/org/sso.md">Third-Party Login (SSO)</a> and <a href="/maiagent-user-guide/en/org/identity-sync.md">Identity Synchronization (LDAP)</a></td></tr><tr><td>Manage Credits and member quotas</td><td><a href="/maiagent-user-guide/en/org/credits.md">Credits Billing</a></td></tr><tr><td>Delete the entire organization when it is no longer used</td><td><a href="/maiagent-user-guide/en/org/organization-management.md">Delete Organization</a>; this cannot be undone</td></tr></tbody></table>


---

# 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.maiagent.ai/maiagent-user-guide/en/org/organization.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.
