​

Settings hub

The Settings hub is the landing grid at /settings that groups every organization-level console into one tile set — the answer to “where do I go to configure this?” when you open the sidebar’s Settings entry. Thirty-six consoles share the grid. This page groups them into families, maps every console to its dashboard route, lists which roles can reach each one, and links every console with an existing guide.

​

What the hub surfaces

Eight families of consoles share the grid, grouped by what they govern:

1. Identity & access. SCIM, Team, Profile, and Security manage who is in the organization and what they can reach.
2. Channels & voice. Voice, Voicemail Boxes, and Channels configure the telephony and messaging channel stack.
3. Messaging & send rules. Frequency Caps, Keyword Rules, Message Suppression, and Personalization govern outbound cadence and content.
4. Quality & CX. CSAT, NPS, QA Autoscore, QA Sampling, and Agents set the QA and customer-experience measurement surface.
5. Data & lifecycle. Retention, Migrations, and Personalization control how long data lives and how it moves between platforms.
6. Billing & org. Billing, Branding, Subaccounts, and General hold the commercial and organizational configuration.
7. Audit & diagnostics. Audit Log, Status, and Reliability surface the operational health and change record.
8. Developer. API Keys, Integrations, and Presence provision the developer access surface.

Every console listed below is one tile on the grid, and the route is the tile’s destination in the dashboard.

​

Console map

​

Role gating

The settings consoles are not equally visible to every team member. The gating matches the org role model used across the dashboard:

• Owner and Admin seats see every console on the grid. Every tile listed above renders for these two roles.
• Developer seats see the developer-facing consoles (API Keys, Integrations, Presence) plus read access to most configuration surfaces, but are gated from billing, billing-sensitive, and org-structural consoles: Billing, Branding, Subaccounts, Team, SCIM, General, and KYC.
• Supervisor seats see the quality and CX consoles (CSAT, NPS, QA Autoscore, QA Sampling, Agents) plus profile-level settings, but are gated from billing, org-structural, and developer consoles.
• Agent seats see Profile, Notifications, Onboarding Status, and the voice-related consoles (Voice, Voicemail Boxes) at read-level, but are gated from every configuration write surface.
• Viewer seats see Profile, Notifications, Status, and Reliability as read-only surfaces; every other console is gated.

The destination page re-checks the role server-side regardless of tile visibility — the grid hide is presentation-only, never an authorization boundary.

​

Worked examples — which console for which task

The most common settings tasks and the console that handles each one:

• Add a team member and assign a role. Open Team, invite by email, pick the role, and send. The invitee receives a join link scoped to the role you assigned.
• Rotate an API key. Open API Keys, find the key, click Rotate. The old key stays valid for a configurable grace window (default 24 hours) so your services do not break.
• Set a per-contact SMS frequency cap. Open Frequency Caps, choose SMS, set the max-sends-per-window and the window length, and save. The cap gates every outbound SMS send to that contact.
• Upload a white-label logo. Open Branding, upload your logo and favicon, set the primary color, and preview. The dashboard and the native chat widget reflect the brand immediately.
• Provision a new WhatsApp channel. Open Channels, choose WhatsApp, complete the embedded WABA-connect flow, and the channel appears in your sending surface once Meta approves the registration.
• Review who changed a setting. Open Audit Log, filter by resource type and date range, and every configuration mutation appears with the actor, timestamp, and before/after diff.
• Check this month’s SLA uptime. Open Reliability, pick the month and channel, and read the percentage with the underlying incident timeline.
• Migrate contacts from another platform. Open Migrations, choose the source connector (Twilio, Telnyx, Sinch, and others), run the dry-run, review the preview, and execute the migration job.
• Schedule data deletion. Open Retention, set the retention window per data class (messages, recordings, audit logs), and the scheduler deletes expired data on the configured cadence.
• Configure SCIM provisioning. Open SCIM, copy the SCIM endpoint URL and bearer token, and paste them into your identity provider (Okta, Azure AD, OneLogin).

​

Decision table — find the right console

​

Guide links — existing deep-dive guides per console

Each of these guides covers one console in depth. Open the hub tile for the surface and the guide for the step-by-step workflow:

​

Concepts behind the consoles

Four concept pages explain the models that the settings consoles lean on:

• Roles, teams, and permissions — how the role model gates every console and API endpoint.
• Tenant isolation — how each organization’s settings are scoped to its own schema.
• Audit ledger model — how every configuration mutation is recorded, searchable, and exportable.
• Tenant compliance defaults model — how compliance posture defaults are set per tenant.

​

See also

• Dashboard home walkthrough — the triage surface that points into every hub including Settings
• API Reference — Settings — the REST API surface for settings endpoints
• Compliance posture overview — the compliance controls that live under Settings / Compliance
• Developer console overview — the API-key and integration surface from the developer’s perspective