Resources
/
Getting started
/
Roles and Permissions
Getting started
Roles and Permissions
What can each member see and do? Learn how roles and permissions control access.
Still stuck?
Our support team can walk you through it
Roles and Permissions
Learn how roles control what every member can see and do in Chekhub, how to build a custom role, and how to scope access by location or project.
Every member in Chekhub is assigned a role, and that role is what determines everything they can do from their very first login — which modules they can open, what they can create or edit, and how much of the organization's data they can see. Chekhub ships with a handful of default roles to get you started, but most organizations end up creating a few of their own to match how their team actually works. Getting roles right early keeps access appropriate as you grow, and makes onboarding new members a lot faster.
Control: permissions determine exactly which modules, actions, and data a role can access.
Scope: each member's Location and Project assignments narrow what they can see, on top of their role, keeping data isolated between teams and customers.
Consistency: defining roles before you invite members means every new hire gets the right access from day one.
Creating a Role
Roles are created and configured directly in the Roles tab's matrix — there's no separate new-role form.
Open the Roles tab: go to the Admin Panel and select the Roles tab.

Admin Panel's Roles tab: permission categories run down the left as expandable rows, and each role is a column of checkboxes across the matrix. Add a new role: click +ADD in the top right. A new column appears at the end of the matrix with its name field ready to type — and +ADD disables until you save or cancel it.

New role column, with its name field active and ready to type — here being named "Safety Officer." Name the role: type a clear, descriptive name directly into the column header, such as "Facility Manager" or "Safety Officer."
Set its permissions: check the boxes down the new column for each category this role needs. Cells you've just changed are highlighted so you can see what's still unsaved.

Safety Officer role with Tickets, PMs, and Rounds checked — highlighted because they're unsaved — and Save/Cancel above the column. Save the role: click Save above the column to commit it, or Cancel to discard it.
Once saved, the role appears alongside the others and is ready to assign to any member from the Members panel.
Cloning an existing role
If a new role is similar to one you already have, it's faster to duplicate it and adjust from there — that's how roles like "Admin Copy" and "Manager Copy" get their names.
Open the options menu: click the ⋮ icon on an existing role's column header.

Role column's options menu, with Clone highlighted — also offering Edit, Activity, and Delete. Select Clone: this adds a copy of that role — such as "Admin Copy" — as a new column, ready to rename and adjust.
The same menu's Edit and Activity options let you rename a role or review a history of changes to it, and Delete removes it.
Configuring Permissions
Permissions live in the same matrix as the role list — categories run down the left, and every role is a column of checkboxes across it. Each category expands into its own list of specifically-scoped permissions, rather than one generic set repeated everywhere.
Find the category: in the Roles tab, locate the category — such as Tickets, PMs, Rounds, Checklists, Logs, Assets, Teams, Members, Projects, Rate Cards, or Training — in the left-hand column.

Roles tab matrix, with permission categories listed down the left-hand column. Expand it: click the chevron next to the category to reveal its individual sub-permissions.

Tickets category expanded — each sub-permission has its own info icon and a column of checkboxes for every role. Check the permissions that apply: work down the role's column, checking or unchecking each permission — a dash means that permission isn't available for that role. Changed cells highlight so you can see what's still unsaved.

Checking permissions for a role — changed cells highlight in orange until you save. Check the description first: click the ⓘ icon next to any permission for exactly what it grants — several look similar at a glance, like the different View and Update scopes below.

Hovering a permission's ⓘ icon shows exactly what it grants. Limit Admin Panel access: only grant Admin Panel permissions to roles that genuinely need to manage organization-wide settings.
Save your changes: click Save above the column to commit them, or Cancel to discard them.

Unsaved changes highlight orange in the column until you click Save.
Tickets, expanded — an example
Every category has its own similarly-detailed list; here's what Tickets breaks down into.
Permission | What it allows |
View All Tickets | See every ticket across the organization. |
View Team Tickets | See tickets assigned to the member's own team. |
View My Created Tickets | See only the tickets the member created. |
Create Tickets | Create new tickets. |
Create Without Templates | Create a ticket without starting from a template. |
Update Tickets | Edit tickets that are still open. |
Update Closed Tickets | Edit a ticket after it's been closed. |
Delete Tickets | Remove tickets. |
Approve Tickets | Approve tickets that require approval. |
Dispatch Tickets | Assign tickets out to a team or vendor. |
Cancel Tickets | Cancel tickets. |
View Ticket Cost / View Team Cost | See cost data on a ticket — the member's own, or their team's. |
A role only needs the permissions its work actually requires — leaving the rest unchecked is not a mistake to fix later.
Assigning a Role and Scoping Access
A role's permissions are the same for everyone who holds it, but how much of the organization's data they can see is set per member — from the Members panel — not on the role itself.
Open the Members panel: go to the Admin Panel, select the Subscription tab, and open the Members panel.

Admin Panel's Subscription tab, with the Members panel listing current members and their roles. Find the member: search by name, email, role, or location, then open their profile.

Member's profile page, opened after searching for them. Update access: click the ⋮ options icon and select Update Access.

Member's profile, with the options menu open to Update Access and Resend Invite. Set the role: choose the member's role from the dropdown.

Setting the role in the Update Access panel. Scope their Locations and Projects: leave these open for organization-wide access, or restrict the member to specific locations or projects — this is what actually isolates a customer, vendor, or department to just their own data.
Save.
Changes take effect immediately — the member's access updates the next time they load Chekhub.
Default Roles at a Glance
Every organization starts with a set of built-in roles — the four core roles below, plus portal-specific roles for customers and vendors. Use them as-is, or copy one as the starting point for a custom role.
Role | Typical access |
Admin | Full system access, including the Admin Panel and all configuration settings — a superuser. |
Manager | Broad oversight and reporting access; can do most of what Admin can, except change organization-wide Admin Panel settings. |
Technician | Completes assigned work — tickets, checklists, and rounds — without broader configuration access. |
Lite | Limited access to create and view checklists, assets, and tickets, with no configuration or admin capability. |
Customer Portal Member (Read Only) | Views their own tickets and account information through the customer portal. |
Customer Portal Admin | Manages users and settings within their organization's customer portal, in addition to their own work. |
Vendor Portal Manager | Oversees their vendor team's work and billing through the vendor portal. |
Vendor Portal Technician | Completes dispatched work assigned to them through the vendor portal. |
Your Roles tab may list a few more portal roles than shown here, depending on your plan — worth a quick check before you build a custom role from scratch.
Best Practices for Roles and Permissions
A few habits keep access accurate as your organization and team change.
Start with roles, then add members: defining roles first means every invitation already has the right access attached.
Apply least privilege: grant only the permissions a role needs today — you can always add more later.
Review roles quarterly: confirm permissions and visibility are still appropriate as people and projects change.
Reserve Admin Panel access: it's rarely necessary outside of system administrators.
