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

# Team roles

> Invite your team to a Rally workspace and choose what each person can do: owner, program admin, content reviewer, finance admin or support manager.

Invite teammates from **Settings → Members** with **Invite**. Pick one or more roles for each person. A person with several roles can do everything any of them allows.

## Roles

| Role | Can |
| - | - |
| **Brand owner** | Everything, including billing and members. |
| **Program admin** | Run programs end to end: rules, briefs, branding, domains, applications, creators, content review, and approving payouts. |
| **Content reviewer** | Review and verify creator content. |
| **Finance admin** | Approve and send payouts, adjust earnings, manage budgets and billing, and run exports. |
| **Support manager** | Answer creators, keep notes, manage knowledge and send announcements. |

## Approving versus sending payouts

Approving a payout and sending it are separate permissions. Program admins can approve; finance admins can approve and send. So a program team can decide who gets paid while finance controls when money moves.

## Agents

AI agents connected over MCP act with the role of the key they use, and actions such as payouts and publishing wait for a person to approve them. See [Approvals and roles](https://docs.runrally.io/mcp/approvals.md).


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