> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zelto.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage your team

> Invite members, set roles, configure your organization, mint API keys, and track usage.

Everything that governs your workspace lives under [Settings](/docs/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:

| Role     | Can do                                                                               |
| -------- | ------------------------------------------------------------------------------------ |
| `member` | Read the workspace.                                                                  |
| `admin`  | Everything a member can, plus invite teammates (as member or admin) and remove them. |
| `owner`  | Everything an admin can; the owner row can't remove itself.                          |

Pending invitations show on the same page with their status (pending, accepted,
or expired), so you can see who hasn't joined yet.

## Share an invite link

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.

To skip links entirely, turn on **domain join** in **Settings → Organization** —
anyone signing in with an email on your verified domain joins automatically.

## 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](/docs/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.

## Mint an API key

One org-scoped key authenticates the [REST API](/api-reference/agents/list-agents) and the
[MCP server](/docs/mcp) — 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. See [Custom & other providers](/docs/integrations/api-call-upload).

## 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](/docs/integrations) drove the volume. If a quota runs out with no
payment method on file, an **Add payment method** prompt opens the billing
portal.

## Related

* [Settings](/docs/settings) — the full reference for every tab.
* [API reference](/api-reference/agents/list-agents) · [MCP](/docs/mcp) — operate the platform programmatically.
* [Reports](/docs/reports) — the org timezone sets the day boundary for day-over-day counts.