Management console
The management console is the operations entry point for Enhanced, signed in with a system administrator account. It does not replace Server Web: users, roles, and the audit log remain in Server Web.
What it does
| Capability | Location |
|---|---|
| Model catalogue and capability overrides | Model catalogue |
| Group visibility, price, default model | Group configuration |
| User bindings | User bindings |
| Subscriptions and refunds | Subscriptions |
| Store review | Store review |
| Users, roles, audit log | Server Web |
Access and permissions
- Sign in with an account that has the system administrator permission.
- Every management action is checked on the server; whether a menu is visible is only a UI detail.
- The management console shares accounts with the Server. On the same browser origin, the session can be reused; a different domain requires signing in again with the same account.
Model catalogue
- Sync the catalogue and inspect sync status, model count, and update time.
- Override capability information: display name, context window, max output, input modalities, vision, Web Search, reasoning, tool calling, cost, and thinking levels.
- When the same model ID appears under multiple providers, bind the correct catalogue entry manually.
- Resetting an override restores the catalogue or built-in information.
See Management console: models and subscriptions for details.
Groups and user bindings
- Only opened groups appear in personal AI settings.
- Each group can set a price (30 days) and a group default model.
- A user must be bound before seeing System AI; unbinding is destructive and clears the user's AI state.
Subscriptions and refunds
- Filter subscriptions by group, user, status, and platform.
- Only active subscriptions are refundable, and a completed order payment must exist.
- A refund revokes the subscription immediately; repeating the action does not refund twice.
Store review
- View the pending queue and version comparisons.
- Inspect screenshots, archive information, and integrity checks.
- Approve, reject, or unlist entries; a rejection must include a reason.
See Publishing to Store for the full workflow.