Settings and Billing
Settings and Billing is where operator access and the organization’s subscription meet the console. Settings shows who you are signed in as and what your session can do; Billing is the subscriptions surface — the organization’s managed Control subscription and enterprise/Edge packages, and the feature grants they confer. The current console also has guarded organization switching and subscription/checkout actions; available actions depend on the account’s state and permissions.
Settings: organization and session
Section titled “Settings: organization and session”The Organization and session panel reports the resolved session: user, organization, role, auth source, the session’s permissions, whether enrollment actions are allowed or read-only, and the selected environment and fleet.
Billing: subscriptions and feature grants
Section titled “Billing: subscriptions and feature grants”Billing reflects the organization’s subscription state — which billing accounts exist, which package is in effect, and which features that package grants. Where available, the console can start the provider’s guarded checkout or customer portal flow. A checkout return alone is not proof of a new Auth Site allowance: wait for provider reconciliation and the effective grant and capacity panels to update. The screen shows these sections, with an explicit unavailable notice when Control does not return data:
- Billing accounts — each account’s name, status (active, suspended, or other), payer kind, and billing email.
- Commercial readiness — check-by-check state: billing account linked, commercial status, readiness status, package, the subscription shell (provider and status), included credits, whether Stripe is integrated (expected false today), whether billing sits on the Auth hot path (expected false), and the linked billing account.
- Effective Feature Grants — each feature’s key, status, effective value (for example a maximum Auth Site count, a day count, or an enabled flag), granting package, and grant source or denial reason.
- Premium feature gate — a single gate check (for example
proof_profile.blindfold) showing whether the premium feature is available and the grant or denial reason.