Workspace settings
Workspace identity, deployment mode, model defaults, budget caps and provider keys.
Settings, General holds the workspace's own configuration. Reading it needs no special role. Changing it is admin only, and an account that cannot change it sees the form as read only rather than getting a save that fails.
The settings overview
Settings on its own is a hub with live counts: members, teams, macros, SLA policies, API keys, phone numbers, provider keys, spend against the monthly cap, allowlist entries, active sessions and audit events in the last week. It is the quickest way to see the shape of a workspace.
General
Deployment mode. How this workspace is using Auralis. It changes which menus appear and how agents deploy.
Name. The workspace name shown throughout the product.
Data region. Where the workspace's data is stored.
Default model and the default embedding model, used where nothing more specific is chosen.
Daily cap and monthly cap. The budget caps that billing measures spend against. An unset cap is not the same as a cap of zero: unset means no cap is configured.
Send only what you are changing. Each setting is written on its own, so saving here cannot revert a change somebody else made to a different setting at the same moment.
Provider keys
Settings, Provider keys stores the credentials for the model, speech, voice and telephony providers a workspace uses. Each provider is a card with its own fields.
Two rules govern every key on that screen:
A stored key is never returned. Not by this screen, not by any operation. The read reports only whether a key is set, as a yes or no per key. If you need to know the value, you need it from the provider, not from here.
Keys are encrypted at rest, stored separately from the workspace's ordinary settings.
To remove a key, save it as empty. That deletes it.
Provider key changes are recorded in the audit log.
Onboarding
First-run setup writes its progress into the workspace settings as you go, so a half-finished setup survives a reload. It is stored as the client wrote it and the service does not interpret it.
Doing it through the API
GET /v1/tenants/me reads the workspace and its settings, including the per-key
flags. PATCH /v1/tenants/me changes them and is admin only. See the
API reference.