> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levelset.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Roles
> Add, rename and reorder your organization's roles, choose which roles can open the dashboard, edit what each role can do, and make custom levels for particular people
## Roles, levels and permission levels
The **Roles** tab is where your organization's job titles become permissions. A **role** is a job title, such as Team Lead (use your own role names); your organization defines its own, and each team member has one at each store. Each role has a **level**, its rank in the order from the top role down, shown in the **Level** column: 0 is the top, the Operator, and a higher number is further down.
Every role also has a **permission level** with the same name: the set of things anyone in that role can do in Levelset. Change it and everyone in the role changes with it. A **custom level** is a permission level made for particular people instead of a whole role. An **admin level** is a permission level for logins that aren't tied to a role, such as office staff added on the [Access](/team/access#add-someone-who-isnt-a-team-member) tab; Levelset creates two, Administrator 1 and Administrator 2.
Open **People > Team & Access** and click the **Roles** tab. Every row is one of your organization's roles, with its level, its **Dashboard** box, how many people hold it (hover the count to see it per store), and **Edit permissions**. Custom levels are listed under the roles. What you can do here depends on your own role; if a button described below is missing, [Who can do what](#who-can-do-what) names the permission.
Here because a permission is missing? Go to [Edit what a role can do](#edit-what-a-role-can-do).
## Edit what a role can do
Say a store wants its Team Leads to see the Evaluations page.
1. On the **Roles** tab, click **Edit permissions** on the role: Team Lead.
2. Find the permission. Open a section, or type in the search box in plain words, for example "fire someone" or "see pay". Here, search "evaluations" and find **View Evaluations**.
3. Tick or untick it. It saves at once.
The permissions are grouped the way the sidebar is, and each one names the part of Levelset it belongs to; the other help pages name permissions the same way, for example Evaluations > View Evaluations. The line under the level at the top of the editor says how many people with a login it affects and, after a change, whose access changed; **Show who has this level** lists them. A permission that needs another says so, for example **(requires View Dashboard)**, and ticking it turns that one on too.
A change applies to everyone on the level at once, at every store. You can edit only the levels of roles below your own, so a role at or above yours shows no **Edit permissions**. To change what one person can do without touching their whole role, make a custom level instead.
## Make a custom level for specific people
Say one Team Lead should also manage the schedule, and the rest shouldn't.
1. On the **Roles** tab, click **Add custom level** under **Custom levels**.
2. Enter a **Permission Level Name**.
3. Pick the **Permission Tier**: the level the custom level belongs to, here Team Lead's. It starts from Levelset's default permissions for that level, not from the role's edited ones.
4. Click **Create**, then **Edit permissions** on the new level to change it.
5. On the [Access](/team/access#change-someones-permission-level) tab, open the person and pick the level under **Permission level**.
A custom level can be given only to people whose role is at that level. To delete one, click its trash icon and **Delete level**. Levelset refuses while people are on it ("N people are on this level. Move them to another level first."), including a login whose access was removed. Admin levels are listed here and can't be deleted.
## Turn dashboard access on or off for a role
The **Dashboard** box decides whether people in the role can open the dashboard at all, separately from what they can do inside. Tick or untick it. A role nobody has set follows the default, shown as **Default: on for the Operator and the two levels below**. Click **Use default** to put a role back on it. The Operator always has the dashboard.
A setting made for one person on the [Access](/team/access#give-or-remove-dashboard-access) tab wins over the role.
## Add, rename or delete a role
| To | Do this |
| - | - |
| Add a role | Click **Add role** under the list. **New Role** appears at the bottom of the order. Type its name in place |
| Rename a role | Click the name, type, and click away. It saves when you leave the field. Any role below yours can be renamed, except the Operator's |
| Change its color | Click the circle beside the name and pick a color |
| Delete a role | Click the trash icon. You can delete only roles below yours, and only once nobody holds the role, including people no longer active. Move them first by [changing their role](/team/team-members#change-someones-role) |
## Reorder roles
Drag a role by the handle on the left of its row to its new place. The level numbers follow the new order, and each role's permission level moves with it. The Operator stays at the top, and a move that involves a role at or above yours is refused when it saves.
## Who can do what
| If you notice this | The permission behind it |
| - | - |
| The **Roles** tab shows only names, levels and people, with no **Dashboard** column | Roles > View Roles, or Permissions > View Permissions |
| No drag handles and no **Add role**, and the **Dashboard** boxes can't be ticked | Roles > Manage Roles |
| No **Edit permissions** buttons and no **Custom levels** | Permissions > View Permissions |
| The permissions editor opens but nothing can be ticked, and no **Add custom level** | Permissions > Manage Permissions |
| No **Edit permissions** on one particular role | Not a permission: that role is at or above yours in the role order |
To give a permission to a whole role, someone whose role is above it opens this tab, clicks **Edit permissions** on the role, and ticks it. For one person only, they make a custom level and pick it for that person on the Access tab. If you're missing something here, ask whoever manages roles in your organization to turn it on.
## Common questions
You can edit only the permission levels of roles below yours. Roles at or above yours in the role order show no button.
Their **Permission level** on the Access tab is a custom level, which doesn't follow the role. Either tick the permission on that custom level, or set them back to **Role default**.