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

# Setting up staffing roles

> Define the roles PlanMyRounds uses to categorise doctors for shift staffing, beyond the standard Senior and Junior split, and see how rank feeds coverage.

A **staffing role** is an organisation-defined category used to staff shifts, for example *Consultant*, *Registrar*, *Senior*, or *On Call 1*. Each role has a **rank**, which the engine uses to work out seniority order.

<Note>
  Staffing roles are an alternative to the standard [Senior and Junior Level](/docs/concepts/seniority-and-senior-junior-mix) field. Until your organisation creates roles here and starts assigning them to doctors, profiles and shifts keep using the standard Level field, and nothing changes for you.
</Note>

## Open Staffing Roles

Go to **Settings**, then **Organization**, then select the **Staffing Roles** tab.

<Note>
  Only admins can view or manage staffing roles.
</Note>

## Create a role

<Steps>
  <Step title="Start a new role">
    Select **Add Role**.
  </Step>

  <Step title="Name it">
    Enter a **Display Name**, for example *Senior Resident*.
  </Step>

  <Step title="Set the role key">
    PlanMyRounds fills in a **Role Key** based on the name, for example `senior_resident`. You can edit it before saving, but not afterward: it's the stable identifier the engine uses internally.
  </Step>

  <Step title="Set the rank">
    Enter a **Rank**. Higher numbers mean more senior. Use gaps between your numbers (10, 20, 30) so you can insert a new role later without renumbering everything.
  </Step>

  <Step title="Save">
    Select **Create Role**. The role is immediately available on doctor profiles and shift requirements.
  </Step>
</Steps>

## Manage existing roles

| Action                      | What it does                                                    |
| --------------------------- | --------------------------------------------------------------- |
| **Move up / Move down**     | Changes a role's rank, and its position in the seniority order. |
| **Edit name**               | Rename a role. The Role Key stays fixed even if you rename it.  |
| **Deactivate / Reactivate** | Hides a role from new assignments without deleting its history. |

## Where staffing roles are used

<CardGroup cols={2}>
  <Card title="Doctor profiles" icon="id-card">
    A doctor gets a **Staffing Role** in place of the standard Level field. See [Doctor profiles](/docs/team/doctor-profiles).
  </Card>

  <Card title="Shift Requirements" icon="clock">
    Instead of a single **Min Seniors Required** number, a Shift Requirement can set a headcount per role, each marked **Exact** or **Minimum**.
  </Card>
</CardGroup>

<Note>
  If you're not sure whether your organisation is set up for staffing roles or the standard Senior/Junior model, check whether doctor profiles show a **Staffing Role** field or a **Level** field. If you need help moving between the two, contact support.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Seniority" icon="star" href="/docs/concepts/seniority-and-senior-junior-mix">
    How the standard Senior/Junior Level field is used across scheduling.
  </Card>

  <Card title="Update a doctor's profile" icon="id-card" href="/docs/team/doctor-profiles">
    Assign a doctor's staffing role.
  </Card>

  <Card title="Coverage requirements" icon="shield-check" href="/docs/concepts/coverage-requirements">
    How Required Doctors and Min Seniors Required work together.
  </Card>
</CardGroup>