> ## Documentation Index > Fetch the complete documentation index at: https://docs.rulebase.co/llms.txt > Use this file to discover all available pages before exploring further. # Roles and permissions > Reference for the seven system roles Rulebase ships with and the permissions each one grants. Every member holds exactly one role, a bundle of permissions. This is the reference for the roles Rulebase ships with and what each can do. To build or change a role, see [Create and manage roles](/guides/access-management/create-and-manage-roles). ## How roles work * **One role per member.** Roles don't stack. To widen someone's access, switch their role or edit the role. Editing a role changes it for everyone who holds it. * **Roles set what someone can do.** What they see is a separate setting, the membership's **Scope**. Scope defaults to the whole organization and can be narrowed to groups, teams, or partners; the picker appears once partners are configured. See [Invite members](/guides/access-management/invite-members). * **Seven system roles** ship with every organization, identical everywhere and not editable. Anything else is a custom role you build. ## System roles | Role | Built for | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | **Administrator** | Owning the organization. Every permission on this page, including settings, integrations, members, and AI agents. | | **Agent** | A front-line agent's view of their own work. No permissions. Works differently from the rest (see [The Agent role](#the-agent-role)). | | **Compliance Analyst** | Reviewing conversations for compliance. Performs evaluations, provides model feedback, and reads reports. | | **Manager** | Running QA org-wide: scorecards, knowledge base, teams, calibrations, evaluations. | | **Member** | Read-only visibility into reports, analytics, and agent performance. | | **Quality Analyst** | Day-to-day evaluating. Performs evaluations, provides model feedback, and reads reports. | | **Team Leader** | Leading a team. Same as Manager, minus scorecards. | **Quality Analyst** and **Compliance Analyst** differ by one permission (Quality Analysts can open conversation risk snapshots). **Manager** and **Team Leader** differ by one too (only Manager manages scorecards). ## Permissions by role This mirrors the **Permissions** checklist in the role dialog: same groups, order, and wording. **Administrator** holds everything (no column); **Agent** holds nothing. A dashed row is Administrator-only. | Permission | Quality Analyst | Compliance Analyst | Manager | Team Leader | Member | | --------------------------------------------------------------------------- | --------------- | ------------------ | ------- | ----------- | ------ | | **People** | | | | | | | Invite new members | — | — | — | — | — | | Manage organization members and their roles | — | — | — | — | — | | Manage teams and their members | — | — | Yes | Yes | — | | **Evaluations & calibrations** | | | | | | | Perform new evaluations on tickets and agents | Yes | Yes | Yes | Yes | — | | Submit manual evaluation feedback for approval | Yes | Yes | Yes | Yes | — | | Can provide evaluation feedback and train the model | Yes | Yes | Yes | Yes | — | | Assign tickets for evaluations | Yes | Yes | Yes | Yes | — | | View evaluation calibrations | — | — | Yes | Yes | — | | Access all conversation risk snapshots and evaluations | Yes | — | — | — | — | | **Knowledge & scorecards** | | | | | | | Manage evaluation scorecards | — | — | Yes | — | — | | Manage knowledge base | — | — | Yes | Yes | — | | **Insights** | | | | | | | View organization-wide reports and analytics | Yes | Yes | Yes | Yes | Yes | | View agents and performance reports | Yes | Yes | Yes | Yes | Yes | | Manage the QA agent roster | Yes | Yes | Yes | Yes | — | | Set and revise performance targets for teams, agents, and brands | Yes | Yes | Yes | Yes | — | | **Settings & integrations** | | | | | | | Configure and manage external system integrations (Zendesk, Intercom, etc.) | — | — | — | — | — | | Manage organization settings | — | — | — | — | — | | **Agents** | | | | | | | View managed agents, runs, and workflow approvals | — | — | — | — | — | | Run managed agents and chat with agents | — | — | — | — | — | | Create, edit, publish, and delete managed agent configs | — | — | — | — | — | | **Instruct** | | | | | | | View Instruct chat threads, artifacts, and shared chats | Yes | Yes | Yes | Yes | Yes | | Send Instruct chat messages, stream responses, and share chats | Yes | Yes | Yes | Yes | Yes | The table does not show: * Anyone with **Perform new evaluations on tickets and agents** can submit a manual evaluation. Without **Can provide evaluation feedback and train the model**, that evaluation counts immediately and also enters validation. Granting the feedback permission lets the member publish directly and makes their feedback eligible for model training. * **Settings & integrations** and **Agents** are Administrator-only in every system role. To let someone else configure integrations or build AI agents, use a custom role. * The **Agents** permission group is the AI agents you build under [Home > Agents](https://app.rulebase.co/home/agents). It has nothing to do with the **Agent** role or the reps on your QA roster. ## The Agent role **Agent** has no permissions by design. Agents don't use the main workspace. Signing in lands them on their own performance portal, where they can: * read their own performance overview and weekly reports * open evaluations of their own tickets * contest an evaluation within your organization's dispute window * complete coaching simulations assigned to them The portal is scoped to their own records **in code**, so no permission checkbox widens it. For a hard data boundary, such as an outsourced reviewer who must never load another partner's conversations, use a scoped membership. Scope is enforced on every conversation query. See [Set up partners](/guides/access-management/set-up-partners). A few Agent-specific quirks: the **Scope** picker is disabled for Agent (and for Administrator); neither can be cloned as the basis for a custom role; and a new member given the Agent role is added to the [QA roster](/guides/quality-assurance/manage-agent-roster) as evaluable. Their tickets start flowing into QA automatically. ## Custom roles When none of the seven fits, build a custom role from the same permissions. Common cases are a validator who reviews evaluations but can't touch member settings, or a knowledge owner who maintains scorecards and nothing else. Most custom roles are a system role plus or minus one permission, so cloning **Quality Analyst** or **Manager** and toggling a checkbox is usually faster than building from scratch. Viewing roles needs no special access; creating, editing, cloning, or deleting one needs **Manage organization members and their roles**. ## Related * [Create and manage roles](/guides/access-management/create-and-manage-roles): create, edit, clone, assign * [Invite members](/guides/access-management/invite-members): set role and scope at invitation * [Assign roles from your identity provider](/guides/identity-provider-role-assignment): map IdP groups to roles * [Create and manage teams](/guides/access-management/create-and-manage-teams)