Skip to main content
Everything that governs your workspace lives under Settings. This guide covers the operational setup a new org needs.

​
Invite members and set roles

From Settings → Members, owners and admins can invite teammates by email and remove them. A teammate’s role is chosen at invite time. Roles, in increasing privilege: The gate isn’t dashboard-only: administering the org over MCP checks the caller’s role too. An API key, though, is scoped to the organization rather than to a role — see Settings → API keys before handing one out. Pending invitations show on the same page with their status (pending, accepted, or expired), so you can see who hasn’t joined yet. Every organization gets a shareable invite link the moment it’s created, shown at the top of Settings → Members (owners and admins only). Anyone with the link can join your organization — they log in or create an account and land in the workspace automatically, no per-email invite needed. New members join with the member role. The link is valid for 30 days. From the same panel you can Copy it, Regenerate it (which immediately invalidates the old URL and mints a new one), or Revoke it (after which the link stops working until you generate a new one). Share it only with people you want in your workspace — anyone who has the URL can join. Membership requires an invitation. An email domain never grants organization access.

​
Configure the organization

Under Settings → Organization, set your name and logo, your timezone, and the default locale new members start in. The timezone is also the day boundary for daily reports and day-over-day call counts, so set it to where your team actually works. The org slug in your URLs is read-only. The organization is your workspace, not a client record. If your team serves several clients or brands, set them up as Companies inside the same organization.

​
Mint an API key

One org-scoped key authenticates the REST API and the MCP server — there’s no separate credential per surface. Mint one under Settings → Integrations → API Call Upload → Create API key; the secret is shown once, so copy it then. Delete a key from the same card to revoke it immediately. Both minting and revoking are owner/admin-only, since a key reads every transcript in the org and outlives its minter’s browser session. It does not outlive their access, though: removing that person from the org (or banning their account) stops their keys and MCP OAuth tokens on the next request. See Custom & other providers.

​
Track usage and billing

The Usage tab meters calls_analyzed (conversations run through analysis) and transcript_minutes (audio Zelto transcribed), each against your monthly quota and any prepaid grant. A usage-by-source breakdown shows which integration drove the volume. Owners and admins can select Add card or Replace card in the permanent Payment method section. Enter the card, authorize saving it and charging agreed invoices when due, then select Save card and complete any bank authentication. Saving makes no payment; canceling or failing a replacement keeps the existing default. Members see whether a card is on file. Quota warnings open this same form; see Usage & billing.
  • Settings — the full reference for every tab.
  • API reference · MCP — operate the platform programmatically.
  • Reports — the org timezone sets the day boundary for day-over-day counts.