What a role and a person's extra permissions each control, the catalog they draw from, and how the two add up to what someone can do.
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
Every person in Bettr Manager can do exactly what their role allows, plus any single permissions you grant them on top. You build the roles on Roles and assign them, one person at a time, on User companies — both under Settings in the sidebar.
Each role sits on its own row, carrying:
Point at a row to reveal its actions: the key icon opens the role's permissions, the pencil edits its name and view, and the trash deletes it. Selecting the role's name opens its Members panel.
Every organization starts with an Administrator role that holds every permission. It is the role the first person holds, and the one you assign to anyone who needs the run of the whole system.
A role's permissions live on their own screen, apart from its name. The catalog there is grouped by area of the app:
Search by name to jump to a permission, or use Select all and Clear all to move quickly. The same catalog appears in the role editor and in a person's Additional permissions.
A role can also be named as a required approver on a recipe version. When it is, the role's members are the people whose sign-off a new version needs. That is why a role still in use on a recipe cannot be deleted until you clear it from those recipes first.
A Search users box sits at the top, and each person has a row with their name and email and three controls:
The row itself does not show the role a person holds; open the Role control to see or change it.
The Manage companies panel lists every company in your organization with a checkbox each. Tick a company to give the person access to it; a Current access tag marks the companies they already belong to. Select all and Clear all move every company at once, a counter reads back how many are selected, and Save commits the change.
The Role panel is a single menu listing every role you have built, plus No role. A person holds one role at a time, so choosing a new one replaces whatever they held before and clears any extra permissions granted on top of it. Save stays disabled until you actually change the selection, so you never re-save the role someone already holds.
The Additional permissions grid is the full catalog again — the same areas and checkboxes as a role. Here you grant one person a single right their role does not carry, without touching anyone else who shares the role. These are .
The permissions the person's role already grants show up ticked and disabled: you can add here, never take a role's permission away from one person. Save changes commits what you ticked.
A person's real access is one sum: everything their role grants, plus anything extra you added on top. The role is the baseline you reuse across a crew; the extras are the exception for one person.
Because the role is the baseline, two changes reset a person's extras:
To take access back, open Role and choose No role — the person keeps only the extras you granted directly. To drop an extra, untick it in Additional permissions and save; you can only untick the extras, since a role's own permissions stay locked.