Administration
The Administration section covers everything an account owner or admin needs to operate the workspace — separate from the day-to-day Builder concerns documented elsewhere.
This section covers:
- Users & RBAC — the five account-level roles, active / inactive / invited user states, and the reinvite flow.
- Projects — creating and organising projects within a workspace. See Studio → Projects.
- Billing, credits & usage — credit-based metering, per-run and monthly estimates, usage analytics (in active development; usage dashboards live in the workspace usage view today).
- Credit usage warnings — account- and project-level monthly credit thresholds with email alerts to admins (default 80%).
- Plans & limits — how features (voice config, Guardrails, vector DB choice) are gated across Free and paid plans; per-plan platform limits.
- Audit logs (admin view) — workspace-wide change history. See Observability → Audit logs.
- Secret managers — workspace-wide secret backing (HashiCorp Vault integration, with planned support for Azure Key Vault, AWS Secrets Manager, and GCP Secret Manager for enterprise tenants).
- Application deletion rules — restrictions when applications are deployed or have dependents. See Studio → Application deletion.
Where Administration sits vs Studio
- Studio handles per-application authoring — the canvas, variables, versioning, deployment of individual apps.
- Administration handles account-wide concerns — who's in the workspace, what they can do, how usage is metered, and which platform-wide limits apply.
Most administrative actions are restricted to Account Admin or Owner roles. Project Admin has scoped control within their projects. See Users & RBAC for the full role definitions.