> This page is for Revenue Guard.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://revenue-docs.creliohealth.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://revenue-docs.creliohealth.com/_mcp/server.

# Organization & users

Your organization is the top-level account that owns everything in Revenue Guard — payers, rules, orders, API keys, webhooks, and both environments. Members of the organization access it with roles that determine what they can do.

## Organization setup

The **Organization Setup** page manages your organization's profile, such as its name and logo. These settings apply across both environments.

![Organization Setup](/_fern-files/_img/2ec8e89b64f63b139cd6555e828b940cf1b35d51eec2b1d666fdda3b3877947c.webp)

## Inviting and managing people

The **User Management** page lists members and pending invitations. Invite a teammate by email and assign them a role; they join once they accept the invitation.

![User Management](/_fern-files/_img/0d15c2749679fa3f7801e211fb4116fb2e795a883830b8802e0249fe080406d3.webp)

## Roles

Access is governed by roles. Each role grants a fixed set of permissions across resources (payers, policies, rules, orders, API keys, and webhooks):

| Role           | Intended for                | Access                                                      |
| -------------- | --------------------------- | ----------------------------------------------------------- |
| **Owner**      | The organization owner      | Full access to every resource.                              |
| **Admin**      | Administrators              | Full access to every resource.                              |
| **Analyst**    | Reviewers and analysts      | Read access, plus submitting and reading orders.            |
| **Integrator** | Engineers wiring up the API | Read access, plus full management of API keys and webhooks. |

When inviting or updating a member you can assign Admin, Analyst, or Integrator. Ownership is transferred as a separate, deliberate action rather than assigned like a routine role.

> **Note**
>
> Roles map to concrete permissions such as `rule:activate`, `apiKey:create`, and `webhook:rotate_secret`. If someone can't perform an action, their role likely doesn't include that permission — an Analyst, for example, can read rules but not activate them.