Roles
Labels like Admin, Editor, or Viewer that group what different kinds of people can do in an app.
What it is
Roles bundle permissions into a few named types of user. Instead of setting rules person by person, you say "Editors can create and edit; Viewers can only read" and assign each person a role.
Keep roles few and tied to real distinctions in your business: Requester, Approver, Admin. Inventing five roles on day one usually means rules nobody understands.
Say who can assign roles, what new users get by default, and whether someone can hold more than one.
How to ask for it
“Managers should be able to do more than regular people.”
“Add two roles: Member (create and edit their own expenses) and Manager (everything Members can do, plus approve or reject anyone's expenses). New users are Members; only Managers can promote someone.”
"Do more" is undefined; naming the roles and listing each one's abilities and defaults makes the rules concrete.
You've seen this in
- SOwner, Admin, and Member in Slack
- GViewer, Commenter, and Editor in Google Docs
- SStaff accounts in Shopify