Roles

What it’s for

A Role bundles together which clusters someone can work in, which menus (modules) they can see, and a couple of special eligibility flags. Every user has exactly one role, and everything they can do in this app comes from it.

Where to find it

Sidebar → Access Control → Roles, at /admin/access-control/roles.

Who can use it

• See the menu item and open the page — needs view.
• See the role list — needs get.
• Create, edit, delete a role — needs create/update/delete.

On this screen

A table of roles, with create, edit, and delete.

How to…

Create a role

1. Click create.
2. Give it a title.
3. Assign at least one cluster — a role with no cluster can’t be assigned to anyone meaningfully.
4. Pick at least one menu — this is what builds the sidebar and gates access, exactly as described in every other page in this documentation’s “Who can use it” section.
5. Optionally turn on any of the eligibility flags (see below).
6. Save.

Field reference

Field	Required	Notes
Title	Yes
Clusters	Yes	At least one
Menus	Yes	At least one — this is the source of every module’s view/get/etc. permissions
Sales-eligible flag	No	Makes members of this role selectable as a Sales PIC on Lead and Sales Activity
Complaint-handler flag	No	Makes members of this role selectable as a technician on Complaint Tickets
Admin flag	No	Stored on the role; not otherwise used within this app

Rules & statuses

The two eligibility flags aren’t cosmetic — they’re the exact filter used elsewhere. Turn off a role’s complaint-handler flag and its members stop appearing in the technician picker; turn off sales-eligible and they drop out of the PIC picker. Neither flag affects menu access, which is controlled entirely by the menus selected above.

Related pages

• Users — where users are assigned the roles created here.
• Complaint Tickets — where the complaint-handler flag determines who can be assigned a ticket.
• Lead — where the sales-eligible flag determines who can be assigned as PIC.