Clearer organization navigation
Organization views now provide clearer navigation across tenants, members, and activity.
From the changelog: Expanded organization management
Authdog Team
Operators who administer more than one tenant used to bounce between organization settings and the environment console without a single place for members, invitations, and activity. Organization views now keep those surfaces on one org-scoped route.
This is the longer note behind the April 14 changelog entry.
How it works
Each organization opens under /organizations/:organizationId. The manage workspace switches modules without leaving the org:
- Profile — organization identity and overview
- Members — membership list and roles
- Invitations — outstanding invites
- Keys — organization keys
- Settings — tenant list and org settings (also reached as
tenants) - Audit — organization activity, including the activity table and heatmap
Membership is shown on the members module and on the operator's own org list, so you can see which organizations you belong to before switching tenants.
Tenant navigation is organization-aware: tenants stay grouped under the org you are managing, instead of a flat list that hides the parent.
Set it up
In the console, open an organization you belong to:
- Confirm Members lists current memberships.
- Use Settings to reach tenants owned by that org.
- Open Audit for organization activity.
Switching tenants still uses the console session. It does not rewrite environment ids or migrate users.
Trust boundaries
Organization navigation only lists orgs and tenants your session can already access. It is not an elevation path. Organization audit is separate from environment audit; do not treat an org activity row as an end-user sign-in event.
Archived organizations stay read-oriented until restored.
Try it
Open an org, switch from Members to Settings, then enter a tenant. Organization concepts are in Organizations. The original release note is in the changelog.