Organizations & teams

Atlas has multi-tenant organizations built into the core, not bolted on as a paywalled afterthought. If your product is B2B — sold to companies whose employees work in teams — organizations are how you model that, from your first commit.

The model

• An organization is a tenant — for example "Acme Inc". It groups users, has its own settings, and owns its own data.

• A user has a personal account and can be a member of many organizations, each with different roles.

• Roles bundle permissions; permissions are the fine-grained verbs your app checks.

• The user's requests carry an active organization context so your app knows which tenant they're acting in.

Why it's isolated at the core

Tenant isolation in Atlas is enforced at the data layer — the repository refuses to read across tenants — so no request can accidentally return another customer's data. This is the same guarantee your compliance reviewers will ask about, and you get it on day one.

What you can do

• Create organizations manually or let users create their own.

• Invite members by email with a chosen role.

• Define custom roles and permissions that match your product.

• Switch a user's active organization and read it from the session.

• Enforce enterprise SSO and SCIM per organization for your largest customers.

In this section

1. Members & invitations — add and manage people in an org.

2. Roles & permissions — model who can do what.

3. Organization context & switching — the active-org concept your app reads.

Availability

Organizations and RBAC are included on the Pro plan and above. See Plans & billing.

Next

Add people to a tenant → Members & invitations.