Overview
The Permissions tab is where administrators control exactly what each user role can see and do in Redlist — from which modules are visible to whether users can create, edit, or delete records.
Accessing Permissions
From the navigation, click Settings, then click User Roles/Permissions. Click the Permissions tab.
How to Configure Permissions for a Role
Select a role and set its access level for each resource in Redlist.
Steps:
Select a role from the Role dropdown at the top of the page.
The permissions table loads showing all available resources for that role.
For each resource, check or uncheck the boxes under View, Create, Update, and Delete to grant or remove access.
Scroll down to the Additional Permissions section to configure any special permissions.
Click Save when finished.
NOTE: Changes are not applied until you click Save. Navigating away before saving will discard your changes.
How to Remove All Access to a Resource
Unchecking all permissions for a resource hides it from users with that role entirely.
Steps:
Select the role from the Role dropdown.
Locate the area or feature you want to restrict in the list.
Uncheck all boxes in that row — View, Create, Update, and Delete.
Click Save.
How to Copy Permissions to a New Role
When creating a new role, you can copy an existing role's permissions as a starting point instead of configuring everything from scratch.
Steps:
Navigate to the User Roles tab.
Click Add User Role.
Enter the new role name.
Select the existing role from the Role Permissions to Copy From dropdown.
Click Create.
Return to the Permissions tab to adjust the copied permissions as needed.
Understanding Additional Permissions
The Additional Permissions section at the bottom of the Permissions tab contains special access settings that fall outside the standard View/Create/Update/Delete model.
Restricted Work Order Access — When turned On, users with this role can only see work orders they are directly assigned to. They cannot view unassigned work orders or work orders assigned to others. Turn this Off to allow the role to see all work orders regardless of assignment.
Use Cases
Setting up a technician role — A reliability manager creates a Technician role and turns on Restricted Work Order Access so each technician only sees their own assigned work. They enable View and Update on Routes but leave Delete unchecked, so technicians can complete tasks but cannot remove route records.
Onboarding a read-only supervisor — A new supervisor needs to monitor progress without making changes. An admin enables only View access across all relevant modules and saves — the supervisor can review routes, assets, and work orders but has no ability to create or edit anything.
Cloning permissions for a new role — A team is adding a Senior Technician role that should have the same permissions as Technician plus the ability to delete work orders. An admin creates the new role using Technician as the copy source, then goes to Permissions and checks Delete for the Work Orders resource.
Locking down a contractor role — A contractor should only see their assigned work orders and nothing else. An admin enables Restricted Work Order Access and removes View access from every module except Work Orders, keeping the contractor's view focused and limited.
Best Practices
Test After Saving: After configuring a role, log in as a user with that role (or ask one to test) to confirm access looks correct before rolling it out broadly.
Use Copy From for Similar Roles: When creating roles with overlapping needs, copy from the closest existing role and adjust — it's faster and reduces the chance of missing a permission.
Review Permissions When Responsibilities Change: If a role's job scope changes, revisit its permissions to make sure access still matches what that role actually does.
Troubleshooting
Issue: A user cannot see a module or feature they need.
Solution:
Go to Settings > User Roles/Permissions > Permissions.
Select the user's role from the Role dropdown.
Find the relevant resource and confirm View is checked.
Click Save, then ask the user to refresh their browser.
Issue: A user can see a module but cannot create or edit records.
Solution:
Open the Permissions tab and select the user's role.
Confirm Create and/or Update are checked for the relevant resource.
Save changes and have the user refresh.
Issue: The Permissions tab is not visible.
Solution:
Confirm your own user role has permission to manage user roles and permissions.
Contact your Redlist administrator to request the appropriate access level.
Summary
The Permissions tab gives administrators precise control over what each role can access in Redlist. Select a role, configure View, Create, Update, and Delete access per resource, set any additional permissions like Restricted Work Order Access, and save. Reviewing permissions regularly ensures every role has exactly the access it needs — no more, no less.