> ## 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.

# Add Users

> Create user accounts, assign system and module roles, and send invitations to bring new teammates into your Mercury workspace.

Add a user when you want to bring a new teammate into your Mercury workspace. The flow is short — enter their details, pick a system role, assign module access, and send the invite.

<Note>
  Users you add **don't get access immediately**. They receive an email invitation and become Active only after accepting it.
</Note>

## What adding a user does

* Creates the user account in your organization
* Assigns a **system role** that defines overall access scope
* Grants **module-level access** (e.g., Recruit) with a specific module role
* Sends an **email invitation** to activate the account

## How to add a user

<Frame>
  <img src="https://mintcdn.com/mercury360/qr2js97eRq-NTgcK/images/add-users-1.png?fit=max&auto=format&n=qr2js97eRq-NTgcK&q=85&s=50d5578fede4288d85663d4d9d7bc744" alt="Add Users 1" width="1913" height="392" data-path="images/add-users-1.png" />
</Frame>

<Steps>
  <Step title="Open User Management">
    From the left navigation panel, click **User Management**.
  </Step>

  <Step title="Click Add User">
    A pop-up form opens on the right side of the screen.
  </Step>

  <Step title="Enter user details">
    Fill in the basic profile information:

    | Field             | Required | Notes                                             |
    | ----------------- | -------- | ------------------------------------------------- |
    | **Email address** | Yes      | Becomes the login — use a valid, accessible inbox |
    | **Full name**     | Yes      | Appears in the user list and on shared activity   |
    | **Phone number**  | Optional | Used for account recovery and notifications       |
  </Step>

  <Step title="Choose a system role">
    Pick one role that defines the user's overall scope. (See [System roles](#system-roles) below.)
  </Step>

  <Step title="Assign module access">
    Select the module (e.g., **Recruit**) and choose a **module role**. The module role determines what they can do *inside* that product.
  </Step>

  <Step title="Send the invitation">
    Click **Send Invite**. The user receives an email and must accept it to activate their account.
  </Step>
</Steps>

## System roles

System roles control a user's **overall access level** across your organization. Pick exactly one per user.

<CardGroup cols={3}>
  <Card title="Organization Admin" icon="crown">
    Full system access. Can manage users, billing, integrations, and organization settings.
  </Card>

  <Card title="Standard User" icon="user">
    Limited access based on the modules and module roles assigned to them.
  </Card>

  <Card title="Limited User" icon="user-lock">
    Restricted access with minimal permissions — ideal for occasional collaborators.
  </Card>
</CardGroup>

<Tip>
  Reserve **Organization Admin** for people who genuinely need to manage billing, users, or org-wide settings. Everyone else should be a Standard or Limited User.
</Tip>

## Module roles

Module roles control what a user can do **inside a specific product** like Mercury Recruit. Common module roles include:

| Module role               | Typical use                                                 |
| ------------------------- | ----------------------------------------------------------- |
| **Recruit Admin**         | Configure the module, manage all jobs, and adjust workflows |
| **Recruit Manager**       | Own hiring for a department, approve jobs and offers        |
| **Recruiter**             | Source, screen, and move candidates through the pipeline    |
| **Interviewer**           | Review assigned candidates and submit scorecards            |
| **External Collaborator** | Limited, scoped access — ideal for agencies or clients      |

## Before you click Send Invite

Confirm:

* The email address is correct
* The system role matches the user’s responsibility
* Module access is assigned correctly
* The user should receive the invite now

## What happens after you invite

The user's status follows a simple lifecycle:

<Tabs>
  <Tab title="Invited">
    The invitation has been **sent**, but the user **hasn't accepted yet**. They can't log in.
  </Tab>

  <Tab title="Active">
    The user has **accepted the invite**. They can log in and use their assigned modules.
  </Tab>

  <Tab title="Inactive">
    The user's access has been **disabled**. They can't log in or use any module.
  </Tab>
</Tabs>

<Frame>
  <img src="https://mintcdn.com/mercury360/qr2js97eRq-NTgcK/images/add-users-2.png?fit=max&auto=format&n=qr2js97eRq-NTgcK&q=85&s=8246681c21bb6592f4aa66947bbadc08" alt="Add Users 2" width="1106" height="774" data-path="images/add-users-2.png" />
</Frame>

## Next steps

<CardGroup cols={2}>
  <Card title="Manage existing users" icon="eye" href="/accounts/user-management/manage-users">
    Search, filter, suspend, or reset passwords for users already in your workspace.
  </Card>

  <Card title="User Management overview" icon="globe-lock" href="/accounts/user-management/overview">
    Review status types, available actions, and how the module fits into Mercury Accounts.
  </Card>
</CardGroup>
