> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizations

> List your organizations, inspect members, and choose the active organization for CLI commands.

Every site belongs to an organization. Your active organization tells the CLI which organization to use by default for organization-scoped commands.

Your personal organization cannot be deleted separately from your account. A refused deletion leaves it active, so you can keep working.

## Activate a team organization

Only your personal organization starts on the Free plan. A new team organization needs a Starter or Pro plan before anyone can use it. Until its first checkout completes, every Studio page of that organization opens **Choose a plan for {organization}**, and its sites, integrations, members, domains, and settings stay unavailable, in Studio, the CLI, and the API alike.

* Owners and admins choose **Continue with Starter** or **Continue with Pro** and complete checkout. Other members see that an owner or admin must activate the organization.
* Leaving checkout without paying keeps the organization inactive. Use the organization switcher at the top of the page to go back to another organization.
* An owner who no longer wants the organization can delete it from the same page.
* A team organization that has paid once stays usable if it later moves to Free.

## List organizations and members

```bash theme={null}
fimo orgs list
fimo orgs members
fimo orgs members --org <organization-id>
```

`fimo orgs list` marks your active organization. `fimo orgs members` shows each member's organization role, email, and name.

## Switch the active organization

```bash theme={null}
fimo orgs switch
fimo orgs switch --org <id-or-slug>
fimo whoami
```

Use the interactive picker in a terminal. In a non-interactive shell, pass `--org`. Run `fimo whoami` to confirm the signed-in user and active organization.

> [!WARNING]
>
> `fimo switch <name>` switches the current Fimo Branch. To change organizations, use `fimo orgs switch`.

## Organization roles and site access

* `member` can create sites and view organization members.
* `admin` can manage organization members, settings, and sites.
* `owner` has full control of the organization.

Site access is a separate choice. A person can belong to an organization without receiving the same role in every site. Open the site's sharing settings to grant `view`, `edit`, or `full` access.

## Move a site to another organization

`fimo projects transfer` moves a site to an organization you administer. There is no Studio equivalent, and the transfer turns off the site's apps. See [Sites and onboarding](/docs/cli/projects.md) for the full procedure.

## What's next

> [card] [Invite collaborators](/docs/collaboration/invite.md)
>
> Choose a site invite or organization invite.

> [card] [Sharing in Studio](/docs/studio/collaboration.md)
>
> Set access for a site from the dashboard.

> [card] [Billing & credits](/docs/collaboration/billing-and-credits.md)
>
> Understand organization-level usage metrics.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.