# Organizations

Manage B2B organizations, their administrators, members, and application access.

Requires: Customer Identity (CIAM)

> **Add-on required:** Organizations are part of the **CIAM** (Customer Identity) add-on. They additionally require the **organizations** feature, available on the Advanced tier and above (and during the Trial).

An **organization** is the container for one external company's users: their roster, the **organization administrators** you delegate their day-to-day management to, and the applications you have approved for them. Organizations are how you run multi-customer (B2B) scenarios without spinning up separate instances.

## Organization vs group vs directory

These three look similar but answer different questions:

- An **organization** models a distinct external business customer — it has its own admins and its own member roster, and you can hand its day-to-day administration to the customer.
- A [**group**](https://dts-identity.com/docs/directories/groups.md) models an assignment bucket inside one population — a convenient way to grant the same apps and roles to many people.
- A [**directory**](https://dts-identity.com/docs/directories/user-directories.md) models *where accounts physically live* — a local directory or a synchronized enterprise (AD/LDAP) directory.

A single user belongs to exactly one directory, can sit in many groups, and can be a member of one or more organizations.

## How organizations relate to users and directories

- An organization's **members** are external users (the **Customers** type — see [People](https://dts-identity.com/docs/directories/people.md)) who belong to a directory of the corresponding business type.
- A user can be a member of one or more organizations.
- Selected members can be made **organization administrators**, giving them delegated control over that organization's users.

### Active organization (members of several organizations)

A session always runs in the context of **one** organization — the *active* organization. It determines the organization details carried in the user's tokens (so connected applications see which customer the person is acting as) and, for an organization administrator, which organization the [Organization portal](https://dts-identity.com/docs/directories/organization-portal.md) manages.

- A member of a **single** organization is placed in it automatically — there is no prompt.
- A member of **several** organizations is asked to **choose an organization at sign-in**. They can tick *Set as default* so that organization is pre-selected next time.
- After signing in, a member of several organizations can change the active organization from their account at any time. The switch is forward-looking: applications they open from then on see the new organization; sessions already established elsewhere are unaffected until they sign in again.

This member-facing selection is separate from the administrator **[Switch organization view](#switch-organization-view)** below, which lets *your* operators scope the console to a customer's data.

## The organizations list

The **Organizations** page lists every organization with its member count and most-recent member activity, and lets you jump by starting letter. A **limit banner** shows how close you are to the number of organizations your subscription includes.

> **Note:** When the Customer Identity add-on is not active, the Organizations area stays reachable so any existing organizations remain manageable, but **creating a new organization is blocked**.

## Creating an organization

1. Open **Organizations** and choose to create one.
2. Enter the **name** and address details, and the business identifiers requested by the form.
3. Save. You are taken to the new organization, with the invitations tab ready so you can invite its first members.

## Members

The organization's **Users** tab lists its members, with administrators shown first.

- **Add users** — select existing users to add to the organization, optionally marking them as organization administrators as you add them.
- **Remove a user** from the organization.
- **Grant or revoke admin** — promote a member to organization administrator or demote them.

You can also **invite** new external users straight into an organization from its **Invitations** tab; see [User lifecycle → Invitations](https://dts-identity.com/docs/directories/user-lifecycle.md#invitations). When you invite someone you can mark them as an organization administrator and pre-authorize the organization's approved applications, both at invite time.

People become members in one of two ways: an admin **explicitly adds or invites** a named person, or a person is added through a self-service flow tied to the organization. Either way, who can join is something you control — keep the trust boundary in mind: anyone who can be onboarded into an organization gains the access shared across it.

## Organization administrators

An **organization administrator** is a member who is delegated management of their own organization — its users and invitations — without being a platform-wide administrator. This lets each business customer run their own user administration while you retain overall control.

An organization admin works in a separate, scoped surface — the **[Organization portal](https://dts-identity.com/docs/directories/organization-portal.md)**. The boundary is firm: they manage only **their own** organization's members and invitations, and have no reach into other organizations or any instance-wide settings.

## Application access

The organization's **Applications** tab defines the organization's **approved set** of [applications](https://dts-identity.com/docs/integrations/applications.md) — the apps that may be handed out to its members. As with groups, each assignment can carry a **validity window** (a start and/or end date); expired assignments drop out of the approved set but remain visible.

Adding an application to the approved set follows the normal permission to assign that app: if the deprecated [**Owners manage access**](https://dts-identity.com/docs/integrations/applications.md#application-owners) is still on for the app, only its owners or a full administrator can add it. If the app belongs to a [workspace](https://dts-identity.com/docs/governance/workspaces.md) with managed access, adding it requires **Manage access** in that workspace (or a responsible or full administrator). Authorizing individual members within the organization is unaffected in both cases, except that the apps of an archived workspace are frozen: organization administrators can neither authorize nor revoke them, and invitations skip them.

Membership in the organization does **not** by itself grant access to these apps:

- **Organization administrators** implicitly hold the organization's entire approved set.
- **Regular members** gain access only to the apps **explicitly authorized for them**, picked from the approved set — access is opt-in. Authorize or revoke them per member from the member's profile (its **Applications** tab), or let the customer's own admin do it in the [Organization portal](https://dts-identity.com/docs/directories/organization-portal.md). When you **invite** a member you can optionally authorize the whole approved set up front.

Removing an app from the approved set immediately revokes it for every member, including any individual authorizations.

[Image: The organization list in the Admin Console]

## Switch organization view

When you administer many customers it helps to see the console *as one organization's data*. **Switch organization view** lets an authorized admin pick an organization and scope the console to that customer:

1. Open the account menu and choose to switch organization view.
2. Select the organization. The console now shows that customer's data.
3. To leave it, end the switched view from the same menu — you return to the full instance.

Who can use it: admins with read access to organizations (lower-privileged viewer-style levels cannot). Both entering and leaving are recorded in the [audit log](https://dts-identity.com/docs/monitoring/audit-logs.md) as **Impersonation Started / Ended**, with the real admin distinguished from the organization being viewed — see [audit event types](https://dts-identity.com/docs/reference/audit-event-types.md).

## See also

- [Organization portal](https://dts-identity.com/docs/directories/organization-portal.md) — the scoped self-service surface an organization admin uses.
- [People](https://dts-identity.com/docs/directories/people.md) — the external users who become members.
- [User directories](https://dts-identity.com/docs/directories/user-directories.md) — the B2B directories that hold organization members.
- [Applications](https://dts-identity.com/docs/integrations/applications.md) — what you assign to an organization.
- [Plans & add-ons](https://dts-identity.com/docs/getting-started/plans-and-addons.md) — CIAM and the organizations feature.
