User permissions control what each person can see and do in CLUE. They help your team give the right access to the right people without giving everyone the same level of control.
Permissions in CLUE are tied to a user’s role. That means access can change based on whether someone is an operator, mechanic, manager, or admin. This keeps day-to-day work simple while still protecting settings, records, and company-wide data.
This setup works closely with the People Directory, Understanding Permissions and Roles, and Managing Job Titles, since those areas help your team review users, roles, and access levels in one place.
Permission levels define what a user is allowed to do in the system. Some users may only need to view data, while others need to create records, edit work, or manage settings.
Common permission levels include:
Roles group permissions together so your team does not have to assign every permission one by one. This makes setup easier and helps keep access consistent across the company.
Common roles include:
The exact permissions in each role can vary depending on how your company sets up roles in Company Settings > Permissions.
Some users can also be limited by division or sub-organization. This means they may only see the assets, projects, and people connected to their own area.
Division-based access can help limit visibility to:
This is useful for companies with multiple regions, yards, or business units that do not all need access to the same data.
You can review a user’s role and access from the People Directory. This is usually the quickest way to confirm what someone should be able to see or do.
To check permissions:
If someone has the wrong access, their role may need to be updated in the permissions setup or in their job title and user record.