Organizations

An organization represents a business customer or partner. Organizations give a person a different set of roles depending on which customer they are acting for, and give each customer its own branded login and connection set.

When to use an organization

Use one when a single person may belong to more than one customer, or when a customer needs its own login experience or identity provider. If your app serves individual consumers, you probably do not need organizations.

Identity and naming

An organization has an immutable name used in URLs and an editable display_name shown to users. Choose the name carefully; it cannot be changed after creation.

Members

Membership records that a user belongs to an organization. Membership by itself grants nothing; roles are assigned per organization on top of it.

Roles within an organization

The same user can be an administrator in one organization and a read-only member in another. The token issued for a session names the organization it was issued for.

Login flows

Connections per organization

An organization can be tied to its own enterprise connection, so its members authenticate against their own directory.

Branding

Logo and colors can be set per organization so the login page matches the customer.

Invitations

Lifecycle

1. Create the organization
2. Enable the connections its members will use
3. Add members and assign their roles
4. Apply branding

Deleting an organization detaches its members; their user records remain.