Workspace administration
Manage organization identity, members, API keys, billing, usage, and destructive workspace actions without confusing organization scope with project scope.
Organization settings apply to the active workspace and every project inside it. Confirm the organization switcher before changing a member, key, plan, or storage connection; the same account can belong to several organizations with different roles.
Open Organization Settings from the organization sidebar. The available pages and actions depend on your role.
General
General changes the organization display name. The current organization avatar is an initials-based display rather than an editable upload. Renaming the organization does not change its slug in existing application URLs, move projects, or rewrite telemetry.
Project names are managed separately under Project → Settings. A project display-name change does not change its project ID, which is the stable value sent by SDKs and used in routes.
Members and roles
Members lists the people in the organization and, for administrators, provides the invite form and role controls.
Before changing a role, open View role permissions and compare the actual capabilities. Only an Owner can assign the Owner role, and an organization must retain at least one Owner. See Roles and permissions for the complete service/action matrix and API-key inheritance behavior.
API keys
Open Organization Settings → API Keys to create a server-side credential. A key has:
- a descriptive title;
- an expiry of one hour, one day, one month, one year, a custom timestamp, or never;
- the member who created it.
The complete value is shown once, immediately after creation. Copy it into a secret manager or an untracked environment file before closing the dialog. The list later shows only a masked value and the last four characters.
Never put an organization API key in browser code, documentation screenshots, source control, or logs. If the full value is lost or exposed, create a replacement, update the client, verify it, and delete the old key.
API keys are organization-scoped. The current dashboard does not assign a role directly to a new key: a role-less key inherits the current organization permissions of its creator, with the API-key safety denylist still applied. Deleting a key revokes it; there is no restore action.
Usage and billing
Usage is the operational view of the current billing period. It shows the plan and renewal date, credits, spans, attachment storage, product availability, and recent Eval and NovaSynth credit activity.
The total credit counter also includes NovaPilot and AI Mapper charges, although those operations do not currently have their own recent-activity table. For exact rates, quota errors, top-up behavior, and current free-plan limits, use Billing, credits and quotas.
Billing shows the active plan, renewal or scheduled plan change, headline usage, available credit packs, plan comparison, and subscription-management controls. Treat the plan and effective limits shown in the workspace as authoritative because organization-specific overrides can differ from published defaults.
Telemetry storage
The organization sidebar’s Telemetry page manages a customer-provided ClickHouse connection. It is separate from the SDK integration page and from model-provider credentials. See Telemetry storage before adding, testing, replacing, or deleting that connection.
Danger zone
Danger Zone deletes the organization, not just the selected project. This is a destructive operation affecting the workspace and its dependent records. It is not an archive, sign-out, or subscription-cancellation control.
Before confirming organization deletion:
- Export any records, reports, or configuration that must be retained.
- Move integrations and production exporters to another organization and API key.
- Verify subscription handling separately under Billing.
- Confirm that other members no longer depend on the workspace.
Use Project → Settings or the Projects directory when you intend to change or delete only one project.