Admin portal and operational readiness policies

Staff who need to see whether an environment is ready for a sensitive workflow should not have to infer it from scattered settings pages. A new admin portal surfaces operational readiness policies for staff oversight, and those policies can gate the workflows they describe.

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

How it works

The admin portal is a staff-level visibility surface. It is not the end-user Account Portal, which hosts sign-in, sign-up, MFA, and profile screens.

Operational readiness policies sit in front of sensitive workflows. If a policy says the environment is not ready, that workflow stays gated instead of failing halfway through a production change.

The same release improves portal and account components used by embedded admin experiences — the shared chrome around hosted admin and account flows, not a new authentication protocol.

Authdog also documents a customer-facing Admin Portal: a short-lived, org-scoped link for a customer's administrator to complete SSO, directory sync, or domain verification without console access. That hosted /admin-portal path is the embedded admin experience these components serve. Do not conflate it with a full console login.

Set it up

For staff oversight, use the admin portal to review readiness policies before you run a gated workflow. Fix the failing checks in the environment (keys, MFA, redirects, or whatever the policy lists), then retry.

For a customer administrator who should not get console access:

1. Authenticate that person in your application and confirm they may administer the organization.
2. From trusted server code, generate a link for one organization and one intent (sso, dsync, or domain_verification).
3. Redirect them to the link immediately. Links expire after 15 minutes.
4. After setup, read or test the resulting configuration. The link is not proof that setup succeeded.

See Admin Portal for the generate-link contract.

Trust boundaries

Readiness policies are gates, not detections. Passing a policy means the configured checks passed at evaluation time. It does not mean the environment is free of abuse. Lidar and audit remain the investigation path.

A hosted admin-portal URL is a temporary bearer credential. Anyone who has it can enter that scoped setup flow until expiry. Never log the full URL. Do not generate links from browser code.

Staff visibility does not replace organization membership checks. Customer admin links are environment-scoped and signed with that environment's active key; generation fails when no active signing key exists.

Try it

Review readiness on a non-production environment, then generate an Admin Portal link for a test organization and one intent. Docs: Admin Portal and Account Portal. The original release note is in the changelog.