Management console: models and subscriptions
System AI administration happens in the management console. Server Web continues to handle users, roles, and the audit log.
Model catalogue
The model catalogue decides capability information: context window, modalities, cost, and thinking levels.
Each model can set:
- Display name, context window, max output tokens;
- Input modalities (text / image), vision, Web Search, reasoning, tool calling;
- Input, output, cache-read, and cache-write cost;
- Thinking-level mapping.
Capability precedence is manual override → catalogue entry → built-in fallback. Web Search and tool calling only come from overrides or built-in data; they are never inferred from the catalogue.
When the same model ID appears under multiple providers, the console flags it as ambiguous and the admin must bind the correct catalogue entry. Resetting an override restores the catalogue or built-in value.
Group configuration
Groups decide which models users can choose. For each group an admin can set:
| Setting | Effect |
|---|---|
| Available to users | Turning it off removes the group from personal AI settings |
| Price (30 days) | Purchase and renewal price for subscription groups |
| Group default model | Optional; must be one of the group's currently supported models |
Only groups opened here appear in personal AI settings. Changes may need a short wait or a page refresh.
User bindings
A user must be bound to System AI before seeing available models.
- Validate / refresh: check the current binding state.
- Bind: enable System AI for the user; an AI account is created if needed.
- Unbind: clear the user's AI state. This is destructive.
The state can be bound, unbound, or unavailable; unavailable usually means the AI service is temporarily unreachable.
Subscriptions and refunds
The subscription list filters by group, user, status, and platform, and shows the subscription period, daily/weekly/monthly usage, paid amount, and refundable amount.
Refund rules:
- Only active subscriptions are refundable.
- A completed order payment must exist.
- The amount must be positive and must not exceed the paid amount.
- Refunds are idempotent; repeating the action does not refund twice.
- A refund revokes the subscription immediately.
Store review
The management console also handles 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; approval makes the new version current and lists it. See Publishing to Store for the full workflow.
Permissions
Every management action requires the system administrator permission. Whether a menu is visible is only a UI detail; the server enforces the permission.