Skip to main content

Settings & provider credentials

Settings is where you bring your own AI and integration providers to the Portal. Agents don't ship with hard-wired model keys — the LLM and Audio tabs only offer a provider once your organization has a credential for it here. This page is also where you manage account preferences, notifications, security and appearance.

Open Settings (/settings).

What's on the Settings page​

The page is a set of tabs. The first four are available to everyone; the rest appear based on your role:

  • General — interface language and timezone.
  • Notifications — email, push and marketing notification preferences. Admins also get a panel to send push notifications.
  • Security — change your password and toggle two-factor authentication.
  • Appearance — light/dark theme, font family, layout density and a color theme picker.
  • API Credentials — provider credentials for AI services and integrations (super admins and org admins).
  • Message Templates — reusable messaging templates (super admins).
  • Global Launch — the platform dialing kill-switch (super admins).
  • Email Delivery — email-sending providers (super admins and org admins), managed in their own tab rather than under API Credentials.

The rest of this page focuses on API Credentials, which is what the agent builder draws on.

API Credentials​

The API Credentials tab is where you register the providers an agent can use. Credentials are grouped into two rows:

  • AI Services — LLM (language model), STT (speech-to-text) and TTS (text-to-speech).
  • Function Integrations — SMS, CRM, Calendar, Ticketing, Payment and Identity. These power the agent's built-in functions (for example, sending an SMS or creating a CRM contact).

Each tab shows a count of how many credentials you've configured for that type. Select a type, then Add Credential to register one.

AI credentials are system-wide; integration credentials are per-organization

LLM, STT and TTS credentials are system-wide, shared across every organization, and managed by super admins — there's no organization selector for them. The integration types (SMS, CRM, calendar, and so on) are scoped to an organization: pick the organization at the top of the tab, and the credentials you add apply to it.

Add a credential​

Add Credential opens a form:

  1. Name — a descriptive label, e.g. "Azure GPT-4o (India)" or "Deepgram Nova-3". Naming with the model and region makes a list of credentials easy to scan.
  2. Provider Type — LLM, STT, TTS, or an integration type.
  3. Provider — the specific provider for that type (see the lists below).
  4. Provider fields — the form then shows exactly the fields that provider needs (API key, endpoint, region, deployment, etc.). Secret fields are masked with a show/hide toggle.
  5. Set as default — optionally mark this credential as the default for that provider, used when nothing more specific is chosen.

Credentials are stored encrypted. The provider type and provider can't be changed after a credential is created — add a new one instead.

AI providers you can add​

  • LLM — Azure OpenAI, Google Gemini, Groq, OpenRouter, and Sarvam AI (Indic languages).
  • STT — Deepgram, Azure Speech, Groq (Whisper), and Sarvam Saarika (Indic).
  • TTS — ElevenLabs, Azure Speech, Groq (Orpheus), Cartesia, Google Gemini TTS, and Sarvam Bulbul (Indic).

The fields depend on the provider. Single-key providers (Deepgram, ElevenLabs, Groq, and similar) just need an API key. Azure OpenAI needs an API Key, Endpoint URL, Deployment Name and API Version — so each Azure credential represents one deployment. Azure Speech needs a Speech Key and a Region.

tip

Add one Azure OpenAI credential per deployment. On the agent's LLM tab, the Azure model list is built from your configured deployments — one credential, one selectable model — so create a credential for each deployment you want agents to choose from.

Integration providers you can add​

These supply the keys the agent's built-in functions use to act on the outside world:

  • SMS — Twilio, Exotel, Meta WhatsApp Business.
  • CRM — HubSpot, Salesforce, Zoho CRM.
  • Calendar — Google Calendar, Microsoft Outlook, Calendly.
  • Ticketing — Zendesk, Freshdesk.
  • Payment — Stripe, Razorpay.
  • Identity — a custom provider.

For Google Calendar and Outlook, the form shows a read-only Authorised redirect URI. Copy it and paste it into your OAuth app — Google Cloud Console (OAuth client → Authorised redirect URIs) or the Azure App Registration equivalent — so the OAuth connection completes.

Manage existing credentials​

Each saved credential appears as a row showing its name, status, provider and a masked key. From the row you can:

  • Enable / disable it with the toggle (a disabled credential stays saved but isn't used).
  • Edit its details.
  • Delete it. Deleting a CRM credential also disconnects the matching CRM integration.

How credentials reach your agents​

Once a credential is enabled here, it becomes selectable in the agent builder:

  • On the LLM tab, the provider list shows only providers your organization has enabled credentials for — and for Azure, the model options come from your deployments.
  • On the Voice & audio tab, the STT and TTS provider lists work the same way.
  • Function Integration credentials power the agent's tools and built-in functions and the CRM integrations.

If a provider you expect isn't appearing on those tabs, the most common reason is that no enabled credential for it exists here.

Next steps​