Settings and billing
Settings and Billing are the Account surfaces for workspace administration.
Settings tabs
Section titled “Settings tabs”The current Settings page has these tabs:
- General for workspace-level configuration.
- Members for workspace access.
- API keys for backend integration credentials.
- Providers for bring-your-own model, speech, telephony, and related provider credentials.
- SSO for workspace single sign-on configuration when available.
- Privacy for privacy controls.
- Compliance for compliance workflows.
- Audit for privileged activity review.
API keys
Section titled “API keys”Workspace API keys are for server-side integrations. Do not place them in browser code, mobile apps, public repositories, or copied widget snippets. Use the dashboard to create, rotate, and revoke keys.
Keys can be scoped broadly with workspace:read or workspace:write, or narrowly by surface. Granular scopes cover agents, knowledge, integrations, tests, phone numbers, schedules, voice bookmarks and provider discovery, User profile fields, memory, Users, conversations, sessions, observability, audit logs, and workspace settings. Sensitive memory, collected data, post-session records, and webhook endpoint management require explicit grants, not coarse workspace grants. API key management itself remains dashboard-only.
Provider credentials
Section titled “Provider credentials”Provider credentials power models, speech, telephony, and other connected services. Store them in Settings, rotate them when ownership changes, and check provider readiness if previews or distribution channels are disabled.
Billing
Section titled “Billing”Billing shows wallet balance, usage, payment methods, top-ups, and auto-recharge.
Current usage meters include voice minutes, text chat messages, WhatsApp messages, test runs, agents, seats, and related wallet-era entitlement limits. Production typed text counts as text chat messages. Voice or realtime audio counts as voice minutes. WhatsApp text replies count as WhatsApp messages. Dashboard previews and tests use separate fair-use limits and do not consume production allowances. Avoid publishing price tables or entitlements from memory; use the dashboard as the source of truth.
Recovery states
Section titled “Recovery states”- Missing provider keys can block previews or channel setup.
- Payment interruptions can block paid-resource usage.
- Wallet-era entitlement limits can block new agents, knowledge uploads, test runs, seats, text chat messages, WhatsApp messages, or voice minutes.
- Missing member permissions can make settings unavailable.