# Organization

> Understand what an organization contains in Flax and manage its settings.

*[View this page in the Flax docs](https://flax-analytics.com/docs/administration/organization)*

An organization is the top-level tenant in Flax. Everything you build — connections, models, dashboards, sheets — belongs to exactly one organization, and every permission and setting hangs off it. Manage yours under `/app/settings/organization`.

## What an organization contains

| Area | What it holds |
| --- | --- |
| People | [Members](/docs/administration/members-and-invitations) and [teams](/docs/administration/teams-and-rbac). |
| Data | [Connections](/docs/connections/overview) and [semantic models](/docs/modeling/overview). |
| Content | Dashboards, charts, and [sheets](/docs/sheets/overview). |
| Governance | [Data entitlements](/docs/administration/data-entitlements), [user attributes](/docs/administration/user-attributes), and [SSO](/docs/administration/sso). |
| Account | [Billing and usage](/docs/administration/billing-and-usage) and the [audit log](/docs/administration/audit-log). |

## Creating and naming an organization

Any signed-in user can create an organization; the creator becomes its first admin. Admins can rename the organization at any time from organization settings.

## Switching organizations

If you belong to more than one organization, you have an **active organization** that scopes what you see across the app. Switching your active org changes your current context; it does not change your membership or role in any org.

> [!NOTE]
> Data is isolated per organization. A query, model, or dashboard in one org is never visible from another — isolation is enforced at the database level. See [Data entitlements](/docs/administration/data-entitlements).

## Next steps

- [Members and invitations](/docs/administration/members-and-invitations)
- [Teams and RBAC](/docs/administration/teams-and-rbac)
- [Billing and usage](/docs/administration/billing-and-usage)