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

> ## Agent Instructions
> To search or read these docs, connect the Ringg docs MCP server at https://docs.ringg.ai/mcp (no key needed; tools search_ringg_ai and query_docs_filesystem_ringg_ai) instead of browsing pages one by one. Setup for each client: https://docs.ringg.ai/resources/mcp-server/docs-mcp-server/mcp-for-ai-assistants.md
> The dashboard labels agents "Assistants"; these docs say "agent". Both mean the same object, identified by agent_id.
> API base URL: https://prod-api.ringg.ai/ca/api/v0. Send the workspace API key in the X-API-KEY header, from server-side code only.
> Placing a call dials a real phone number and spends credits. Confirm the number with the user before calling.
> To act on a Ringg workspace (place calls, edit agents, read transcripts), use the separate Ringg workspace MCP server at https://mcp.ringg.ai/mcp: https://docs.ringg.ai/resources/mcp-server/workspace-mcp-server/overview.md

# Roles and access

> Each Ringg Analytics role sees only the calls and pages it needs: agents their own calls, team leads their team, QAs and admins the whole workspace.

Every member of a Ringg Analytics workspace has one role. The role decides which calls they can open and which pages they see; the server enforces the same rules, so a hidden page's data can't be fetched another way.

In [Ringg Analytics](https://analytics.ringg.ai): **Sidebar → Team** (owners and admins).

## Roles

| Role | Calls they see | Pages | Can also |
| - | - | - | - |
| **Owner** | All | All | Everything an admin can. Set when the workspace is created. |
| **Admin** | All | All, plus **Team** and **Settings** | Manage members, agents, metrics, notifications and dispute settings; reassign disputes; delete and reprocess calls |
| **QA** | All | All except **Team** and **Settings** | Add calls, [review](/analytics-platform/review-calls/qa-reviews) calls, resolve [disputes](/analytics-platform/disputes/review-a-dispute), set up notifications, coach agents |
| **Team lead** | Their team: the agents who report to them, directly or further down | **Summary** (their team), **Interactions**, **Agents** (their team, read-only), **Metrics** (read-only) | Leave coaching notes on their agents' [report cards](/analytics-platform/coach-agents/report-cards) |
| **Agent** | Their own | **Summary** (their own), **Interactions**, **My report card**, **Metrics** (read-only) | [Dispute](/analytics-platform/disputes/raise-a-dispute) an AI score |
| **Member** | All | All except **Notifications**, **Team** and **Settings** | Read only |

A team lead sees the workspace average as a benchmark, but never another team's figures. An agent sees no team or workspace figures at all.

## Invite members

**1. Invite QAs, admins and members from Team**

Click **Invite User**, enter the name and email, and pick the role. For a QA, also pick the **Review mode** and whether they must **Rate and comment on every parameter** (see [QA settings](#qa-settings)).

**2. Add agents and team leads from Agents**

Adding an agent with an email invites them and links their login to their agent record, which is what limits them to their own calls. See [Agents and teams](/analytics-platform/coach-agents/agents-and-teams).

> [!TIP]
>
> The invite arrives by email, and the member shows **Invite pending** until they sign in.

An agent or team lead whose login isn't linked to an agent record sees no calls. Their **Summary** says "Your login isn't linked to an agent yet".

## QA settings

Set per QA when you invite them, or later from the icon next to their role on **Team**.

| Setting | What it does |
| - | - |
| **Review mode: Blind review** (recommended) | The QA scores calls without seeing the AI. AI scores, reasoning and summaries show as `***`, and pages built on AI scores (**Summary**, **Business**, **Agents**, **Analytics**, **Notifications**) are hidden. |
| **Review mode: Full view** | The QA sees AI scores, reasoning and summaries next to the rubric, plus the dashboards. |
| **Rate and comment on every parameter** | The QA can't save a review until every parameter has a rating and a comment. |

## Next steps

> **[Agents and teams](/analytics-platform/coach-agents/agents-and-teams)**
>
> Build the team structure team leads are scoped to.

> **[QA reviews](/analytics-platform/review-calls/qa-reviews)**
>
> How QAs score calls by hand.

> **[Disputes](/analytics-platform/disputes/overview)**
>
> How agents challenge an AI score.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.