Skip to content
English
  • There are no suggestions because the search field is empty.

User Role Permissions

 What is User Role Permissions?

User Role Permissions is the admin page where you create and edit roles that limit what a user can see and access in EZ Ops. Each role is a named set of permissions; you assign a role to a user, and the role narrows their view down to only the modules and reports you choose. A role with no permissions does not restrict anything, so roles are an opt-in way to give certain users a focused, limited view of the app.

Key point: A role only ever narrows access. It works on top of a user's access level and location assignments — it never grants access to a location or feature the user wouldn't otherwise have.

Why It Matters
  • Limit users to what they need - A contractor or single-purpose user can be locked to one module (e.g. only Inspections) instead of seeing every feature their locations expose
  • Cut down task noise for field users - The "Tasks Assigned to Me" permission shows an operator only their own work instead of every task at their assigned locations
  • Reuse a configuration across many users - Define the limited view once as a role, then assign that same role to everyone who should have it
How Role Permissions Work

Understanding these rules prevents the most common configuration mistakes:

  • No permissions = full access - If a role has no permissions listed, it places no restrictions on the user. They can access all organization features their access level and locations allow. The role list shows "No restrictions" for these roles.
  • Any permission = restricted - As soon as you add one or more permissions, the user is limited to only those selected modules and reports. Everything not listed becomes hidden.
  • Admins always bypass roles - Users at access level Admin (3) and EZOPS Team (4) ignore role restrictions entirely. Role permissions only take effect for Employee (2) and Report Viewer (5) users.
  • Only enabled features appear - The permission dropdown only lists modules and reports your organization actually has turned on, so the options vary by organization.
  • Labels follow your org's terminology - If your organization renames features, the permission labels match. For example, "Task" options appear as "Work Order" and "Misc Items" appears as "Inventory" when those renames are enabled.
Permission Options

Permissions fall into three groups in the dropdown:

  • Tasks - Either All Tasks or Tasks Assigned to Me (you can pick only one of the two)
  • Modules - In-app features such as Logbooks, Tanks, Inspections, Schedules, Pigging, Equipment, and so on
  • Reports - Either All Reports or specific reports such as Task Report, Inspections Report, or Logbook Report

A few behaviors to know:

  • The two task options are mutually exclusive - Once you add All Tasks or Tasks Assigned to Me, the other one disappears from the dropdown. Remove the existing task permission to switch to the other.
  • "All Reports" replaces individual reports - Selecting All Reports clears any individually selected reports, and selecting an individual report clears All Reports.

The Special Case: Tasks Assigned to Me

Tasks Assigned to Me is the one option that changes how much of a feature a user sees rather than just whether they see it. With this permission, a user sees only the tasks assigned directly to them or to a department they belong to — along with the items attached to those tasks, such as schedules, inspections, or follow-up tasks. This is instead of seeing every task at their assigned locations, which is what All Tasks gives them.

Use Tasks Assigned to Me for field users who should focus on their own work, and All Tasks for users who need full visibility of everything happening at their locations.

How to Create a Role
  1. Open the Org Configuration menu - In the top navigation, open Org Configuration, expand Users & Roles, then select Roles to open the User Role Permissions page. (You must be an Admin or EZOPS Team user to see this page.)
  2. Click "Add Role" - Located at the top right of the role list. This opens the Add Role window.
  3. Enter a Name - Give the role a clear, descriptive name (this is what appears when assigning the role to a user).
  4. Add permissions - Click Add Permission, then choose a module or report from the dropdown. Repeat for each module or report this role should be limited to.
  5. Leave permissions empty for full access - If you add no permissions, the window shows "No Restrictions" and the role will not limit the user.
  6. Click Confirm - The role is saved and appears in the role list.

[Image placeholder: Add Role window showing the Name field, the Add Permission button, and a permissions dropdown]

How to Edit an Existing Role
  1. Open the User Role Permissions page - Org Configuration menu, Users & Roles, then Roles.
  2. Click the edit (pencil) icon - On the row for the role you want to change. This opens the Edit Role window.
  3. Adjust the name or permissions - Add permissions with Add Permission, change a row using its dropdown, or remove a permission with the trash icon next to it.
  4. Click Confirm - Changes are saved. Affected users see the updated access on their next sync.
How to Assign a Role to a User

A role only takes effect once it is assigned to a user.

  1. Open the user - Go to the Users page and create or edit a user.
  2. Select the Role - Use the required Role dropdown, which lists every role you have created.
  3. Save the user - The role's permissions apply to that user. Remember that the restriction only affects Employee and Report Viewer users — Admins and EZOPS Team users are unaffected.
How to Delete a Role

Deleting a role always moves its users to another role — you cannot delete a role without selecting a replacement.

  1. Open the User Role Permissions page and find the role.
  2. Click the delete (trash) icon on that role's row. The Delete Role confirmation opens, showing how many users currently have the role.
  3. Select a replacement role - Choose the role that every user on this role should be re-assigned to. This selection is required to proceed.
  4. Confirm the deletion - All users are moved to the replacement role, and the deleted role and its permissions are removed.

Common Issues

"I added permissions to a role but the user still sees everything"

  • Confirm the user's access level. Admin (3) and EZOPS Team (4) users bypass all role restrictions — role permissions only limit Employee (2) and Report Viewer (5) users.
  • Confirm the role with the permissions is actually assigned to that user on their profile.
  • Have the user sync; permission changes apply on their next sync.

"A module or report I want isn't in the permission dropdown"

  • The dropdown only lists features your organization has enabled. If a module isn't turned on for the org, it won't appear as a permission option.

"I expected this role to give a user access to something new, but it didn't"

  • Roles only narrow access; they never grant it. The user still needs the right access level and location assignments for anything a role permits.

Remember: An empty role means full access, not no access — adding zero permissions leaves the user unrestricted. Only add permissions when you actually intend to limit what that role can see.