Organizations group tenants and members

Tenants were the top of the console tree, which made billing and membership awkward once several workspaces belonged to the same company. A dedicated organizations concept now groups tenants and members in the console.

This is the longer note behind the July 18 changelog entry.

How it works

The hierarchy is Organization > Tenant > Project > Environment. An organization holds tenants through organization–tenant links. It does not hold projects directly.

Organization records group related tenants and members. Members are account administrators (admin, member), not end users in an environment's user store. Removing a membership revokes console and API access scoped to that organization without deleting the underlying user account.

The release also tightened organization flow UIs: logo placement and navigation so the org you are in is visible in the shell, and tenant-scope handling so actions stay on the tenants that organization actually links.

Opening Organizations clears the selected project. The page sits above a project, so the sidebar collapses to the workspace-only view until you pick a project again.

This page groups your Authdog account. It is not a per-environment customer directory for the users of your app. Model B2B customers as tenants or projects, each with their own environments and user store.

Set it up

In the Authdog console:

1. Open Organizations and create an organization (name and optional description).
2. Link existing tenants to that organization.
3. Invite members with a role. Optional tenant access on the invite can grant entry to specific tenants when they accept.
4. Confirm the organization name appears in the breadcrumb and on the org filter rail for Tenants and Projects.

Accounts with no organization still work. Navigation starts at the tenant list.

Trust boundaries

Organization membership is an admin boundary. It is not an elevation path into an environment you cannot already reach. Switching organization in the console or CLI clears lower scope (tenant, project, environment) so you do not act on the wrong subtree.

The subscription tier is set per organization and inherited by linked tenants. Do not create one organization per end-customer company unless that company is a separate Authdog account boundary.

Tenant-scope fixes in this release are about keeping actions inside the linked set. They do not move users, signing keys, or sign-in methods — those stay on the environment.

Try it

Create an organization, link a tenant, and confirm logo and breadcrumb on a project page. Model and UI: Organizations (concept) and Organizations in the console. The original release note is in the changelog.