An **organization** is the account boundary above a tenant: _"Group existing tenants under an organization and centralize billing."_ It is where the subscription lives, and where you consolidate several tenants that belong to the same company.

![Organizations](/content/console/organizations.png)

The hierarchy is **Organization > Tenant > Project > Environment**. An organization holds tenants; it does not hold projects directly.

## Organization list

The header reads **"Organizations"**, with a card/table view toggle, an **All subscriptions** filter, and a **"New Organization"** button.

Each organization card shows:

- The label **Organization** and a subscription-tier badge (for example `ENTERPRISE`)
- The organization name and description
- A **tenant count** badge
- The last-updated time
- A copy button for the organization ID

Use the **All subscriptions** dropdown to filter by tier when you administer many organizations.

## Create an organization

1. Click **"New Organization"** — or use the **"+"** button in the top bar.
2. Enter a name and optional description.
3. Existing tenants can then be linked to the organization.

Once linked, the organization name appears in the console breadcrumb ahead of the tenant, and in the organization filter rail on the [Tenants](/docs/console/tenants) and [Projects](/docs/console/projects) pages.

## Why the level exists

Two reasons:

**Billing.** The subscription tier is set per organization, so several tenants can share one contract rather than each carrying its own plan. The tier shown on a tenant card is inherited from its organization.

**Administration.** Grouping tenants under an organization gives you a filter that follows you around the console — the org rail on Tenants and Projects, and the leading breadcrumb segment on every module page.

> **Warning**
>
> Opening Organizations clears the selected project, because the page sits above
> a project in the hierarchy. The sidebar collapses to the workspace-only view;
> pick a project again from the [Projects hub](/docs/console/projects) to return
> to environment-scoped modules.

## Organizations in the console vs in your app

Do not confuse this with B2B organizations *inside* your own application. This page groups **your** tenants for billing and administration. Modelling customer organizations, memberships, and invitations for the users of your app is a separate feature — see [Organizations](/docs/organizations) and [Multi-tenancy](/docs/concepts/multi-tenancy).

## Related

| Read | To learn how to |
|------|-----------------|
| [Tenants](/docs/console/tenants) | Create the workspaces an organization groups |
| [Billing](/docs/console/billing) | Set up plans and subscriptions for your own customers |
| [Organizations concepts](/docs/concepts/organizations) | Understand the account boundary in depth |
| [Organizations](/docs/organizations) | Model B2B organizations for the users of your app |