Operator console overview

The operator console manages accounts, registration review, plans and billing, and product-level configuration. It opens within the workspace; it is not a separate public administration domain.

Three permission layers

1. Account session: proves that you are signed in to JumpCLI.
2. Operator grant: the account must hold an active platform-operator grant. An organization owner/admin membership permits workspace Settings only and is not a platform-operator grant.
3. Operator step-up verification: an authorized operator must also use the independent ADMIN_KEY to create a short-lived session before performing sensitive actions.

Regular users and organization administrators do not gain operator capabilities by knowing the step-up-verification format. Do not put step-up verification keys in documentation, chat, or frontend configuration.

Main modules

Module	Purpose
Registration review	Approve or reject registrations awaiting review
Account management	Enable, suspend, and view account lifecycle events
Billing	Maintain plans, subscription bindings, billing projections, and fulfillment status
Settings	Manage model presets, service connectivity, storage, and notification configuration

Operating sequence

For an initial launch, complete base configuration and health checks first; then create plan drafts, publish purchasable plans, and finally make a test-account purchase. Account review, billing, and settings each retain an audit boundary so user-support operations do not become mixed with system configuration.

Continue with Account review and management.