Administration
Open Administration from your account menu to manage your Capacitor server. The destinations you see depend on your role, plan, and the services enabled on your deployment.
Find the right page
Section titled “Find the right page”| Navigation group | Pages |
|---|---|
| People | Members and Invitations, Teams |
| General | Getting started, Plan, Sessions |
| AI & models | AI Providers, Embeddings, Insights and Summaries |
| Evals | Evals and Eval Queue, Eval Catalog |
| Flows | Flows, Flow Catalog |
| Work Items | Work Items and Work item operations |
| Integrations | Integrations and Machines |
| Identity Merge | Merge legacy identities |
| Repositories | Repository aliases |
Getting started (/admin/getting-started) shows your server’s setup checklist when that service is available. Its navigation badge shows completed required items against the required total. Back to app returns to the main dashboard.
The former Assistants page redirects to Summaries. The former General settings page redirects to Sessions. GitHub authentication health is now under Integrations.
Who can administer
Section titled “Who can administer”On tenants with managed organization membership, owners and organization admins can manage Members, Invitations, and Plan. The remaining console pages require server administration access. An organization admin on a shared deployment does not automatically have instance-wide settings access.
On deployments where membership comes directly from the identity provider, manage membership there; the console does not offer managed invitations or native teams. A deployment’s authentication configuration determines its administrators.
An owner can promote a member to admin, demote an admin, or transfer ownership from Members. For a locked-out server, an operator can use the deployment’s Auth:Admin:UserIds setting to grant administrative access.
Saving settings
Section titled “Saving settings”AI settings pages have a Save button. Secret fields show whether a value is set without revealing it: leave a field blank to keep the stored value, enter a replacement, or select Clear on save and save to remove it. Fields supplied by environment variables are locked in the form.
Settings saved through the console are persisted in the server’s settings store; secret values are encrypted at rest. Runtime settings reload without a server restart. Per-repository and per-project switches save immediately, as indicated beneath their tables. Maintenance operations that need a restart say so explicitly.
For first-time configuration, follow Setup Server.