Back to journal

Stop copying UUIDs: browse Authdog identity scope

Navigate organizations, tenants, projects, and environments as one connected hierarchy with Authdog CLI.

A

Authdog Team

2 min read
Four-level organization, tenant, project, and environment hierarchy

Identity platforms contain nested resources, and each API call often needs one or more IDs from that hierarchy. Copying those values between browser tabs, environment files, and terminal commands creates friction and makes stale context hard to spot.

Authdog CLI turns the hierarchy into a guided picker.

Open the navigator

Launch authdog-cli, sign in with /login, then enter:

text
/browse

/navigator is an alias for the same workflow. The CLI walks through four levels:

  1. Organization
  2. Tenant
  3. Project
  4. Environment

Each choice narrows the next API request. Escape returns to the previous level, so correcting a choice does not require restarting the flow.

Handle accounts without organizations

Not every Authdog account belongs to an organization. When the organization list is empty, the navigator skips that step and starts from all available tenants.

For organization-backed accounts, tenant results are filtered to the selected organization. This prevents a merged tenant response from presenting unrelated resources in the same picker.

Persist a complete active scope

Selecting an environment saves the whole path:

  • organization ID when present
  • tenant ID
  • project application ID
  • environment ID

Use /status to inspect the active selection later. The CLI restores persisted scope when it starts again, making repeated exploration faster.

Use focused pickers when needed

The full navigator is not always necessary. These commands open individual parts of the hierarchy:

  • /organizations or /orgs selects an organization.
  • /tenants selects a tenant.
  • /tenant displays the active tenant.
  • /tenant <uuid> selects a validated tenant.
  • /tenant clear removes tenant scope.
  • /projects selects a project for the current tenant.

/projects requires an active tenant because project listings are tenant-scoped.

Read-only by design

The beta navigator selects existing resources. It does not create tenants, promote environments, or change project configuration. This makes it useful as a context browser and debugging tool while keeping management operations outside the current CLI surface.

One connected hierarchy removes much of the mechanical work from identity exploration: choose what you mean, verify it with /status, then keep moving.