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

# Roles & Permissions Overview | Understand Access Levels

Understand access levels and choose the right role for each user.

Roles control what a user can **see**, what they can **do**, and which areas of the system they can **access**. Roles are assigned when a user is created and can be reviewed anytime.

## What roles control

A user’s role determines:

* Which modules they can access
* Which actions they can perform
* How much control they have over system settings and data

## When to use this

Use this page when you need to:

* Understand what each role means
* Decide which role to assign to a user
* Compare access levels between roles
* Review permissions before granting access

## Available roles

<CardGroup cols={2}>
  <Card title="Organization Owner" icon="crown">
    Highest level of access with full control across the system.
  </Card>

  <Card title="Organization Admin" icon="shield">
    High access for managing users and settings, without owner-level control.
  </Card>

  <Card title="Standard User" icon="user">
    Access to assigned modules with limited settings access.
  </Card>

  <Card title="Limited User" icon="lock">
    Minimal permissions for restricted or external access scenarios.
  </Card>
</CardGroup>

### Organization Owner

* Full control over the entire system
* Can manage billing, settings, users, and all modules
* Highest level of access

### Organization Admin

* Can manage users and system settings
* Can access all or most modules depending on configuration
* Cannot override ownership-level controls

### Standard User

* Can access assigned modules only
* Can perform day-to-day operations
* Limited access to system configuration

### Limited User

* Restricted access to specific features only
* Minimal permissions
* Used for external or constrained-access users

## How roles are assigned

Roles are assigned during user creation. After assignment, the role determines:

* What modules the user can access
* What actions they can take inside each module
* What system-level settings and data they can control

## What to be careful about

<Warning>
  Assign roles using least-privilege: give the minimum access needed to do the job.
</Warning>

* Assigning a higher role than needed increases security risk
* Assigning a lower role may block required work
* Role selection directly affects the user’s experience and available workflows