All Collections
Users
Roles & Permissions
Limble Permissions Library
Limble Permissions Library

Permissions in Limble and Default Permissions for Each Role

Rachel Link avatar
Written by Rachel Link
Updated this week

Overview

In Limble, permissions are used to allow users to perform actions and see information about your organization within Limble.

Instead of configuring permissions for individual users, roles are groupings of permissions that are assigned to users by location.

By default, Limble offers Technician, Manager, and View Only as default roles. In addition to these, custom roles allow you to configure unique permission sets. Global permissions are only available to Super Users.

This article covers our entire permissions library and which permissions are included by default with the Technician, Manager, and View Only roles.

Many permissions have dependencies on other permissions in order to function properly, so read each permission description carefully.

Table of Contents

Open Tasks

Included in this section (click on the permission to expand the description!):

View My Open Tasks (#42)

What it does: This allows a user to view open tasks assigned to themself, their role, or their team.

This permission is often used with 'Edit and Complete My Open Tasks (#44)' so that the user can also edit and complete their tasks.

Dependencies: Enabling 'View All Open Tasks (#35)' will override this permission. If you do not want a user with this role to view all open tasks, including tasks that are not assigned to them, make sure to disable permission #35.

Default Roles: Technician, Manager

Edit and Complete My Open Tasks (#44)

What it does: This allows a user to edit or complete open tasks assigned to themself, their role, or their team.

This permission is often used with 'View My Open Tasks (#42)' so that the user can edit and complete their tasks.

Dependencies: Enabling 'Edit and Complete Any Open Tasks (#23)' will override this permission. If you do not want a user with this role to edit and complete all open tasks, including tasks that are not assigned to them, make sure to disable permission #23.

Default Roles: Technician, Manager

View All Open Tasks (#35)

What it does: This allows a user to see all open tasks, including tasks that are unassigned or assigned to other users or teams.

This permission is often used with 'Edit and Complete Any Open Tasks (#23)' so they can also edit and complete all tasks.

When this permission is enabled, the user with this role will see the ‘Manage Work’ navigation item on the web application. If it is disabled, they will see the ‘Open Tasks’ navigation item instead.

Dependencies: None

Default Roles: Manager, View Only

Edit and Complete Any Open Tasks (#23)

What it does: This allows a user to edit and complete all open tasks, including tasks that are unassigned or assigned to others.

If you only want a user to be able to see all tasks at a location, but not complete them, enable ‘View All Open Tasks #35’ and leave this permission disabled.

If this permission is disabled, the user will only be able to see a preview of the task.

Dependencies: 'View All Open Tasks (#35)' must be enabled for this permission to work.

Default Roles: Manager

Start New Tasks (#43)

What it does: This allows a user to start new tasks such as PMs and WOs.

Dependencies: Other permissions may restrict the ways a user can start a task. For example, if 'View All Open Tasks (#35)' is disabled, the user won't see the ‘Manage Work’ page. Therefore, they would be unable to start a work order from there.

Default Roles: Technician, Manager

Submit a Work Request (#45)

What it does: This allows a user to submit a work request within the mobile and web applications.

Dependencies: This permission does not control if someone can submit a work request through the work request portal. Since the work request portal is open to anyone (even those without logins), permissions cannot be applied to control access.

Default Roles: Technician, Manager, View Only

Change Assignments of Open Tasks (#26)

What it does: This allows a user to reassign an open task. This permission includes bulk reassignments.

Dependencies: None

Default Roles: Technician, Manager

Change Due Dates of Open Tasks (#46)

What it does: This allows a user to reassign an open task. This permission includes bulk reassignments.

Dependencies: None

Default Roles: Manager

Change an Open Task’s Priority Level and Task Status (#101)

What it does: This allows a user to change the priority level of an open task and the task status.

By default, Limble offers 3 priority levels: 1 - High Priority, 2 - Medium Priority, and 3 - Low Priority. If permission #101 is enabled, the user can also edit and add priority levels.

By default, Limble offers 3 task statuses: Open, In Progress, and Complete. If permission #101 is enabled, the user can also edit and add task statuses.

If this permission is disabled, the user can only view priority levels.

Dependencies: None

Default Roles: Technician, Manager

Edit an Open WOs Instructions (#47)

What it does: This allows a user to edit instructions and settings of an open work order (WO).

Dependencies: If this is enabled, the user should also have 'Edit and Complete Any Open Tasks (#23)' enabled.

Default Roles: Manager

Edit an Open PMs Instructions (#103)

What it does: This allows a user to edit instructions and settings of an open preventative maintenance task (PM).

Dependencies: If this is enabled, the user should also have 'Edit and Complete Any Open Tasks (#23)' enabled.

Default Roles: Manager

Edit an Open Work Requests Instructions (#104)

What it does: This allows a user to edit problem report instructions and settings of an open work request (WR).

Dependencies: If this is enabled, the user should also have 'Edit and Complete Any Open Tasks (#23)' enabled, since WRs or problem report instructions often need to be adjusted.

Default Roles: Technician, Manager

Delete Open Tasks (#24)

What it does: This allows a user to delete open tasks.

Use caution when enabling this permission: once a task is deleted, it cannot be restored.

Dependencies: None

Default Roles: Manager

Override Automatic Task Timer (#183)

What it does: This allows a user to change the time shown when they click ‘Log Time’ or ‘Complete’ in a task, also known as the task timer.

If this permission is disabled, a user cannot change the time entered in the task timer. If they want to add additional time spent on a task, they would need to open the task and wait until the task timer catches up to the initial time they entered in the task timer.

They will also be unable to enter less time in the task timer, so if they accidentally enter an amount larger than their time spent, they will be unable to correct their mistake.

We do not advise disabling this permission. If you choose to disable this permission, be sure to provide adequate staff training on how to use the task timer properly.

Dependencies: None

Default Roles: Technician, Manager

Log Time for Other Users (#166)

What it does: This allows a user to log time on tasks for other users.

Dependencies: None

Default Roles: Manager

Add Parts to Open Tasks (#167)

What it does: This allows a user to add new parts to open tasks.

If this permission is disabled, the user will still be able to enter how many parts were used if parts are already included in the task template.

Dependencies: None

Default Roles: Technician, Manager

Add Invoices to Open Tasks (#168)

What it does: This allows a user to add invoices to open tasks.

Dependencies: None

Default Roles: Technician, Manager

Tag a Task with a Custom Tag (#173)

What it does: This allows a user to add or remove a custom tag to a task. This permission does not allow them to edit, add, or remove tag options.

Only Super Users can create custom tags.

Dependencies: None

Default Roles: Technician, Manager

Add Task Comments (#178)

What it does: This allows a user to add comments onto a task.

Dependencies: None

Default Roles: Technician, Manager

Remove Task Comments (#174)

What it does: This allows a user to remove comments from a task.

Dependencies: None

Default Roles: None

Merge and Recreate Work Requests (#177)

What it does: This allows a user to merge work requests, and recreate a work request using any custom work request templates created on their organization’s account.

This permission allows a user to reselect the correct work request template if the work requester mistakenly triggered the wrong template based on their submission.

Dependencies: None

Default Roles: Technician, Manager

Export Tasks (#181)

What it does: This allows a user to export open and completed tasks from Limble.

Dependencies: None

Default Roles: Technician, Manager, View Only

Print or Share Tasks (#182)

What it does: This allows a user to share tasks with others, including people who do not have a Limble account.

This permission includes the ability to:

  • Print a task as a PDF

  • Send an internal link to another Limble user

  • Share the task externally to work on a task (commonly used for vendors)

Dependencies: None

Default Roles: Technician, Manager, View Only

Edit My Task Comments (#203)

What it does: This allows a user to edit their task comments. It does not give a user the ability to edit other user's comments. Once a comment is changed, it will be indicated as "(edited)" in the comment log.

If a user is already mentioned or newly added to an edited comment, they will not be notified. If sharing comments with work requesters is enabled, they will not be notified about edits to comments.

Dependencies: Comments can only be edited in an open task state. If a task has been completed, users with permission #48 'Edit Completed Tasks' can reopen the task to allow a user to edit their comment.

Default Roles: None

Click here to go back to the Table of Contents.

Completed Tasks

Included in this section (click on the permission to expand the description!):

View My Completed Tasks (#108)

What it does: This allows a user to view completed tasks assigned to them.

Dependencies: Enabling 'View All Completed Tasks (#109)' will override this permission. If you do not want a user with this role to view all completed tasks, including tasks that were not assigned to them, make sure to disable permission #109.

Default Roles: Technician, Manager, View Only

View All Completed Tasks (#109)

What it does: This allows a user to see all completed tasks, including tasks that were assigned to others.

Dependencies: Most reports are created using task data such as asset downtime, time spent on tasks, etc. If permissions #109 and/or #108 are disabled for a user with this role, their reports may not be accurate due to missing or incomplete data.

Default Roles: Technician, Manager, View Only

View and Edit Labor Costs (#142)

What it does: This allows a user to see labor costs, including billable hours and billable rates, if your team uses Labor Categories in Limble.

Labor costs can only be viewed in a completed task state.

Dependencies: Permission #48 ‘Edit Completed Task,’ must be enabled for this permission to work, as billable hours and billable rates can only be seen in a completed task state.

Default Roles: Manager, View Only

View Invoices (#186)

What it does: This allows a user to view invoices on open and completed tasks.

Dependencies: None

Default Roles: Technician, Manager, View Only

Edit Completed Tasks (#48)

What it does: This allows a user to reopen and edit information on completed tasks. Enable this permission carefully: it allows the user to change work and task history.

This permission allows both the user with this role and the user assigned to the task to make changes to the task.

When edits are made to a completed task, a comment will be added indicating the task was edited.

Dependencies: None

Default Roles: Manager

Delete Completed Tasks (#49)

What it does: This allows a user to delete completed tasks. Use caution when enabling this permission: once a task is deleted, it cannot be restored.

If this permission is disabled, the user will not see the button that allows them to delete a completed task.

Dependencies: None

Default Roles: Manager

Import Completed Tasks (#100)

What it does: This allows a user to import completed tasks into Limble. This permission includes bulk imports.

Use caution when enabling this permission: when done improperly, bulk imports can be tedious and time-consuming to fix.

Dependencies: None

Default Roles: Manager

Export Completed Tasks (#195)

What it does: This allows a user to export completed tasks.

Dependencies: None

Default Roles: Technician, Manager, View Only

Click here to go back to the Table of Contents.

Work Requests

Included in this section (click on the permission to expand the description!):

Setup and Configure Work Request Portal (#105)

What it does: This allows a user to configure your work request portal(s) to show or hide fields, and set which fields are required for someone to submit a work request.

This permission excludes the global work request portal, unless the user is a Super User.

Dependencies: None

Default Roles: Manager

Click here to go back to the Table of Contents.

Dashboards

Included in this section (click on the permission to expand the description!):

View Global Dashboard (#112)

What it does: This allows a user to view the Global Dashboard.

Dependencies: None

Default Roles: Technician, Manager, View Only

View Custom Dashboards (#41)

What it does: This allows a user to access custom dashboards. Permission #41 must be enabled for all other custom dashboard permissions to work.

Permission #41 is often used with ‘Add Custom Dashboard (#113)’ so the user can view shared custom dashboards and create their own.

Without enabling #113, they will only be able to view custom dashboards that have been shared by other users.

Dependencies: None

Default Roles: Technician, Manager, View Only

Add Custom Dashboard (#113)

What it does: This allows a user to add new custom dashboards.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Copy Custom Dashboard (#114)

What it does: This allows a user to add new custom dashboards.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Delete Custom Dashboards (#115)

What it does: This allows a user to delete custom dashboards.

Use caution when enabling this permission: once a dashboard is deleted, it cannot be restored.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Reorder Custom Dashboard Widget (#120)

What it does: This allows a user to edit the name of their custom dashboards. They cannot make changes to custom dashboards that were shared by others.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Share Custom Dashboards (#121)

What it does: This allows a user to share their custom dashboards with other users.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Print Custom Dashboards (#179)

What it does: This allows a user to print their custom dashboards as a PDF.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Add Custom Dashboard Widget (#116)

What it does: This allows a user to add widgets (such as graphs, charts and lists) to a custom dashboard. This permission should be turned on if you want a user to create custom dashboards.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Copy Custom Dashboard Widget (#117)

What it does: This allows a user to duplicate widgets (such as graphs, charts and lists) on a custom dashboard.

This permission should be paired with permissions #120, #116, #118, and #119 if you want a user to make changes using the custom dashboard feature’s full functionality.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Delete Custom Dashboard Widget (#118)

What it does: This allows a user to delete widgets (such as graphs, charts and lists) from a custom dashboard.

This permission should be paired with permissions #120, #116, #117, and #119 if you want a user to make changes using the custom dashboard feature’s full functionality.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Edit Custom Dashboard Widget (#119)

What it does: This allows a user to edit widgets (such as graphs, charts and lists) in a custom dashboard.

This permission should be paired with permissions #120, #116, #117, and #118 if you want a user to make changes using the custom dashboard feature’s full functionality.

Dependencies: ‘View Custom Dashboards (#41)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Click here to go back to the Table of Contents.

WO Templates

Included in this section (click on the permission to expand the description!):

Add WO Templates (#122)

What it does: This allows a user to add new WO templates or duplicate existing WO templates.

Dependencies: ‘Start New Tasks (#43)’ must be enabled for this permission to work.

Default Roles: Manager

Delete WO Templates (#123)

Use caution when enabling this permission: once a WO template is deleted, it cannot be restored.

Dependencies: ‘Start New Tasks (#43)’ must be enabled for this permission to work.

Default Roles: Manager

Click here to go back to the Table of Contents.

PM Templates

Included in this section (click on the permission to expand the description!):

View Manage PMs (#27)

What it does: This allows a user to access the ‘Manage PMs’ page.

Permission #27 must be enabled in order to use permissions #50-58 and #189.

Dependencies: None

Default Roles: Manager, View Only

Add PMs (#50)

What it does: This allows a user to add or duplicate existing PM templates.

Dependencies: ‘View Manage PMs (#27)’ must be enabled for this permission to work.

Default Roles: Manager

Delete PMs (#51)

What it does: This allows a user to delete PM templates.

Use caution when enabling this permission: once a PM template is deleted, it cannot be restored.

Dependencies: ‘View Manage PMs (#27)’ must be enabled for this permission to work.

Default Roles: Manager

Bulk Delete PMs (#52)

What it does: This allows a user to bulk delete PM templates.

Use caution when enabling this permission: once a PM template is deleted, it cannot be restored.

Dependencies: ‘Delete PMs (#51)’ and ‘View Manage PMs (#27)’must be enabled for this permission to work.

Default Roles: Manager

Edit PMs (#53)

What it does: This allows a user to edit PM templates.

This permission includes instructions and settings, but does not include assigning an asset, user, or schedule to a task.

Dependencies: ‘View Manage PMs (#27)’ must be enabled for this permission to work.

Default Roles: Manager

Change or Assign an Asset to PM (#54)

What it does: This allows a user to change or assign an asset to PM templates.

Dependencies: ‘View Manage PMs (#27)’ must be enabled for this permission to work.

Default Roles: Manager

Change PM Schedules (#55)

What it does: This allows a user to add, delete, or change a schedule on PM templates.

Dependencies: ‘View Manage PMs (#27)’ must be enabled for this permission to work.

Default Roles: Manager

Change PM Assignments (#56)

What it does: This allows a user to change or assign a user to PM templates.

Dependencies: ‘View Manage PMs (#27)’ must be enabled for this permission to work.

Default Roles: Manager

Bulk Update PMs (#57)

What it does: This allows a user to bulk update a group of PM templates.

Use caution when enabling this permission: when done improperly, bulk updates can be tedious and time-consuming to fix.

Dependencies: ‘View Manage PMs (#27)’ and most other PM permissions must be enabled for this permission to work.

Default Roles: Manager

Import PMs (#58)

What it does: This allows a user to import and bulk import PM templates.

Use caution when enabling this permission: when done improperly, bulk updates can be tedious and time-consuming to fix.

Dependencies: ‘View Manage PMs (#27)’ must be enabled for this permission to work.

Default Roles: Manager

Export PMs (#189)

What it does: This allows a user to export PMs as a .csv file.

Dependencies: ‘View Manage PMs (#27)’ must be enabled for this permission to work.

Default Roles: Manager, View Only

Click here to go back to the Table of Contents.

Assets

Included in this section (click on the permission to expand the description!):

View Manage Assets (#39)

What it does: This allows a user to access the ‘Manage Assets’ page.

Dependencies: None

Default Roles: Manager, View Only

View Look up an Asset (#110)

What it does: This allows a user to look up an asset and see asset information without editing it.

Dependencies: If permission #39 is enabled, the user will not see the ‘Look Up an Asset’ page on the desktop application.

Default Roles: Technician, Manager, View Only

Add Assets (#60)

What it does: This allows a user to add or duplicate existing assets.

Dependencies: ‘View Manage Assets’ (#39) must be enabled for this permission to work on the desktop application. However, users can still add assets via the mobile app if #39 is disabled.

Default Roles: Manager

Delete Assets (#61)

What it does: This allows a user to delete assets.

Use caution when enabling this permission: once an asset is deleted, it cannot be restored.

Dependencies: None

Default Roles: Manager

Bulk Delete Assets (#62)

What it does: This allows a user to bulk delete assets.

Use caution when enabling this permission: once an asset is deleted, it cannot be restored.

Dependencies: ‘Delete Assets (#61)’ must be enabled for this permission to work.

Default Roles: Manager

Change Asset Name (#63)

What it does: This allows a user to change an asset’s name.

Dependencies: None

Default Roles: Manager

Change Asset Image (#99)

What it does: This allows a user to upload or change an asset’s picture.

Dependencies: None

Default Roles: Manager

Configure Asset Fields (#64)

What it does: This allows a user to change the fields within an asset. This includes adding and removing existing fields from an asset, but does not include the ability to create or delete new fields.

‘View Manage Assets (#39)’ must be enabled for the user to change if a field is viewable by users who only have ‘View Look Up an Asset (#110)’ enabled.

Dependencies: None

Default Roles: Manager

Edit Asset Field Values (#66)

What it does: This allows a user to change the values of asset fields.

Even if this permission is disabled, a user will still be able to change an asset field’s value in a PM instruction.

Dependencies: None

Default Roles: Technician, Manager

Create and Delete Asset Fields (#65)

What it does: This allows a user to create and delete new asset fields.

Use caution when enabling this permission: this allows a user to remove all fields from all assets. Once a field is deleted, it cannot be restored.

Dependencies: None

Default Roles: Manager

Manage Asset Logs (#67)

What it does: This allows a user to manage asset logs. This includes the ability to edit, delete, or mark a log as private.

Dependencies: ‘View Manage Assets (#39)’ must be enabled for this permission to work.

Default Roles: Manager

Edit Asset Settings (#68)

What it does: This allows a user to edit information in the asset settings. This includes hours of operation, asset start date, and the ability to move an asset’s location.

Use caution when enabling this permission.

Dependencies: None

Default Roles: Manager

Change Asset Hierarchy (#59)

What it does: This allows a user to change an asset’s hierarchy. This includes moving assets to be parent or children assets to other assets.

Dependencies: None

Default Roles: Manager

Import Assets (#69)

What it does: This allows a user to import assets into Limble.

Dependencies: None

Default Roles: Manager

Export Assets (#188)

What it does: This allows a user to export assets as a .csv file.

Dependencies: None

Default Roles: Manager, View Only

Asset Check In/Out (#196)

What it does: This allows a user to check in and check out assets marked as tools.

Dependencies: None

Default Roles: Technician, Manager

Bypass Tool Check Out Approval (#197)

What it does: This allows a user to bypass an approval process (if applicable) when checking out a tool.

Dependencies: ‘Asset Check In/Out (#196)’ must be enabled for this permission to work.

Default Roles: Manager, View Only

Click here to go back to the Table of Contents.

Parts

Included in this section (click on the permission to expand the description!):

View Manage Parts (#40)

What it does: This allows a user to access the ‘Manage Parts’ page.

Dependencies: None

Default Roles: Manager, View Only

View Look up a Part (#111)

What it does: This allows a user to look up a part and see part information without editing it.

Dependencies: If permission #40 is enabled, they will not see the ‘Look Up a Part’’ page on the desktop application.

Default Roles: Technician, Manager, View Only

Change Part Name (#70)

What it does: This allows a user to change a part’s name.

Dependencies: None

Default Roles: Manager

Change Part Number (#71)

What it does: This allows a user to change a part’s number.

Dependencies: ‘View Manage Parts (#40)’ must be enabled for this permission to work.

Default Roles: Manager

Manually Change Part Qty (#72)

What it does: This allows a user to manually change a part’s quantity, or how many parts are in your inventory.

Dependencies: None

Default Roles: Technician, Manager

Change Part Price (#73)

What it does: This allows a user to change a part’s price.

Dependencies: None

Default Roles: Manager

Change Part Location (#74)

What it does: This allows a user to change a part’s location.

Dependencies: None

Default Roles: Manager

Change Part Vendor (#75)

What it does: This allows a user to change a part’s associated vendor.

Dependencies: None

Default Roles: Manager

Change Part Category (#76)

What it does: This allows a user to change a part’s category.

Only Super Users can delete part categories.

Dependencies: None

Default Roles: Manager

Manage Parts Log (#77)

What it does: This allows a user to manage part logs. This includes the ability to edit, delete, or mark a log as private.

Dependencies: None

Default Roles: Manager

Create Part/Asset Associations (#78)

What it does: This allows a user to associate a part with an asset and vice versa.

Dependencies: None

Default Roles: Manager

Create Part/Vendor Associations (#141)

What it does: This allows a user to manually associate a part with a vendor and vice versa.

Dependencies: None

Default Roles: Manager

Change Part Settings (#79)

What it does: This allows a user to change part settings, including all threshold settings.

Dependencies: None

Default Roles: Manager

Change Part Image (#98)

What it does: This allows a user to change a part’s image.

Dependencies: None

Default Roles: Manager

Delete Parts (#80)

What it does: This allows a user to delete parts.

Use caution when enabling this permission: once a part is deleted, it cannot be restored.

Dependencies: None

Default Roles: Manager

Bulk Delete Parts (#81)

What it does: This allows a user to bulk delete parts.

Use caution when enabling this permission: once a part is deleted, it cannot be restored.

Dependencies: ‘Delete Parts (#80)’ must be enabled for this permission to work.

Default Roles: Manager

Add Parts (#82)

What it does: This allows a user to add parts.

Dependencies: ‘Delete Parts (#80)’ must be enabled for this permission to work.

Default Roles: Manager

Import Parts (#172)

What it does: This allows a user to import parts.

Use caution when enabling this permission: when done improperly, bulk updates can be tedious and time-consuming to fix.

Dependencies: None

Default Roles: Manager, View Only

Configure Part Fields (#169)

What it does: This allows a user to change the fields within a part. This includes adding and removing existing fields from a part, but does not include the ability to create or delete new fields.

Dependencies: None

Default Roles: Manager, View Only

Edit Part Field Values (#170)

What it does: This allows a user to change the values of custom part fields. This does not include static fields such as part name or number.

Dependencies: None

Default Roles: Manager, View Only

Create and Delete Part Fields (#171)

What it does: This allows a user to create and delete new custom part fields.

Use caution when enabling this permission: this allows a user to remove all custom fields from all parts. Once a field is deleted, it cannot be restored.

Dependencies: None

Default Roles: Manager, View Only

Transfer Parts from Location (#187)

What it does: This allows a user to transfer part quantities between locations within Limble.

The user does not need to have this permission turned on for each location to transfer part quantities, but they need to have some level of access to the location receiving the parts.

Dependencies: None

Default Roles: Manager

Export Parts (#190)

What it does: This allows a user to export parts as a .csv file.

Dependencies: None

Default Roles: Manager, View Only

Click here to go back to the Table of Contents.

Teams

Included in this section (click on the permission to expand the description!):

View Manage Teams (#29)

What it does: This allows a user to access the ‘Manage Teams’ page.

Permission #29 must be enabled for all other teams permissions to work.

Dependencies: None

Default Roles: Manager, View Only

Add or Remove a User from a Team (#83)

What it does: This allows a user to assign users to a team and remove users from a team.

Dependencies: ‘View Manage Teams (#29)’ must be enabled for this permission to work.

Default Roles: Manager

Edit Teams (#84)

What it does: This allows a user to add, delete and rename teams.

Dependencies: View Manage Teams (#29)’ must be enabled for this permission to work.

Default Roles: Manager

Click here to go back to the Table of Contents.

Maps

Included in this section (click on the permission to expand the description!):

View Maps (#198)

What it does: This allows a user to access the ‘View Maps’ page.

Dependencies: None

Default Roles: Technician, Manager, View Only

Configure Maps (#199)

What it does: This allows a user to add, edit, and delete maps.

Dependencies: ‘View Maps (#198)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Copy Maps (#200)

What it does: This allows a user to copy or duplicate maps.

Dependencies: ‘View Maps (#198)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Share Maps (#201)

What it does: This allows a user to share their maps with other users.

Dependencies: ‘View Maps (#198)’ must be enabled for this permission to work.

Default Roles: Technician, Manager, View Only

Configure Asset Maps (#202)

What it does: This allows a user to add, edit, and delete the map location on an asset.

Dependencies: ‘View Maps (#198)’ must be enabled for this permission to work.

Default Roles: Manager

Click here to go back to the Table of Contents.

Vendors

Included in this section (click on the permission to expand the description!):

View Manage Vendors (#124)

What it does: This allows a user to access the ‘Manage Vendors’ page.

Dependencies: None

Default Roles: Manager, View Only

View Look up a Vendor (#125)

What it does: This allows the user to see vendor information without editing it.

Dependencies: If permission #124 is enabled, they will not see the ‘Look Up a Vendor’ page on the desktop application.

Default Roles: Technician, Manager, View Only

Add Vendor (#126)

What it does: This allows the user to add vendors.

Dependencies: None

Default Roles: Manager

Delete Vendors (#127)

What it does: This allows a user with this role to delete vendors.

Use caution when enabling this permission: once a vendor is deleted, it cannot be restored.

Dependencies: None

Default Roles: Manager

Bulk Delete Vendors (#128)

What it does: This allows a user to bulk delete vendors.

Use caution when enabling this permission: once a vendor is deleted, it cannot be restored.

Dependencies: ‘Delete Vendors (#127)’ must be enabled for this permission to work.

Default Roles: Manager

Change Vendor Name (#129)

What it does: This allows a user to edit a vendor’s name.

Dependencies: None

Default Roles: Manager

Change Vendor Email (#130)

What it does: This allows a user to edit a vendor’s email address.

Dependencies: None

Default Roles: Manager

Change Vendor Phone (#139)

What it does: This allows a user to edit a vendor’s phone number.

Dependencies: None

Default Roles: Manager

Change Vendor Contact (#140)

What it does: This allows a user to edit a vendor’s contact. The contact would be the person you interact with on behalf of the vendor’s organization.

Dependencies: None

Default Roles: Manager

Change Vendor Image (#131)

What it does: This allows a user to edit a vendor’s image.

Dependencies: None

Default Roles: Manager

Configure Vendor Fields (#132)

What it does: This allows a user to change the fields within a vendor profile. This includes adding and removing existing fields from a vendor profile, but does not include the ability to create or delete new fields.

Dependencies: None

Default Roles: Manager

Edit Vendor Field Values (#133)

What it does: This allows a user to change the values of custom vendor fields. This does not include static fields such as vendor name, email address, and phone number.

Dependencies: None

Default Roles: Technician, Manager

Create and Delete Vendor Fields (#134)

What it does: This allows a user to create and delete new custom vendor fields.

Use caution when enabling this permission: this allows a user to remove all fields from all vendors. Once a field is deleted, it cannot be restored.

Dependencies: None

Default Roles: Manager

Edit Vendor Settings (#135)

What it does: This allows a user to edit information in the vendor settings. This includes the ability to move a vendor’s location and edit their start date.

Dependencies: None

Default Roles: Manager

Import Vendors (#136)

What it does: This allows a user to import vendors.

Use caution when enabling this permission: when done improperly, bulk updates can be tedious and time-consuming to fix.

Dependencies: None
Default Roles: Manager

Manage Vendor Logs (#137)

What it does: This allows a user to manage vendor logs. This includes the ability to edit, delete, or mark a log as private.

Dependencies: None

Default Roles: Manager, View Only

Create Vendor/Asset Associations (#138)

What it does: This allows a user to manually associate a vendor with an asset and vice versa.

Dependencies: None

Default Roles: Manager, View Only

Export Vendors (#194)

What it does: This allows a user to export vendors as a .csv file.

Dependencies: None

Default Roles: Manager, View Only

Click here to go back to the Table of Contents.

POs

Included in this section (click on the permission to expand the description!):

View Purchase Order (PO) Page (#143)

What it does: This allows a user to access the ‘Purchase Order’ page and view all POs.

If permission #143 is disabled, they will still be able to look at POs linked to their assigned tasks and parts.

Dependencies: None

Default Roles: Manager, View Only

Start a PO (#144)

What it does: This allows a user to start a PO from a task or part viewer.

Dependencies: None

Default Roles: Technician, Manager

Delete PO (#145)

What it does: This allows a user to delete a PO.

Use caution when enabling this permission. Once a PO is deleted, it cannot be restored. Deleting a PO will result in the following:

  • All associated PO items and bills will be deleted

  • Any received invoices or parts will be reverted

  • Parts or services will be removed from their associated tasks as if they were never used

Users who do not have this permission can still delete POs assigned to them if the PO is in set-up mode.

Dependencies: None

Default Roles: Manager

Edit and Complete My POs (#184)

What it does: This allows a user to edit and complete their own POs.

Dependencies: This permission will not override instances where the PO is not in an editable status, or if a step in the budget’s workflow does not allow for PO to be edited.

Default Roles: Manager

Edit and Complete Any POs (#185)

What it does: This allows a user to edit and complete any POs.

Dependencies: This permission will not override instances where the PO is not in an editable status, or if a step in the budget’s workflow does not allow for PO to be edited.

Default Roles: Manager

Change PO Vendor (#146)

What it does: This allows a user to add or change a PO’s vendor.

Users who do not have this permission can still change the vendor in POs assigned to them if the PO is in set-up mode.

Dependencies: 'Edit and Complete My POs (#184)' or 'Edit and Complete Any POs (#185)' must be enabled for this permission to work.
Default Roles: Manager

Change PO Budget (#147)

What it does: This allows a user to add or change a PO’s budget.

Users who do not have this permission can still change the vendor in POs assigned to them if the PO is in set-up mode.

Dependencies: 'Edit and Complete My POs (#184)' or 'Edit and Complete Any POs (#185)' must be enabled for this permission to work.

Default Roles: Manager

Change PO Assignment (#148)

What it does: This allows a user to change which user is assigned to a PO.

Users who do not have this permission can still change a PO’s assignment if it is currently assigned to them and the PO is in set-up mode.

Dependencies: 'Edit and Complete My POs (#184)' or 'Edit and Complete Any POs (#185)' must be enabled for this permission to work.

Default Roles: Manager

Change PO Details (#149)

What it does: This allows a user to change the details of a PO, including:

  • PO date

  • Expected delivery date

  • Custom field values

  • Notes to vendor

  • Billing and shipping recipients

This permission does not include the ability to create PO fields or change PO items.

Users who do not have this permission can still change the details of POs assigned to them if the PO is in set-up mode.

Dependencies: 'Edit and Complete My POs (#184)' or 'Edit and Complete Any POs (#185)' must be enabled for this permission to work.

Default Roles: Manager

Configure PO Fields (#150)

What it does: This allows a user to create and delete new custom PO fields, often used for terms and conditions.

Dependencies: 'Edit and Complete My POs (#184)' or 'Edit and Complete Any POs (#185)' must be enabled for this permission to work.

Default Roles: Manager

Change PO Items (#151)

What it does: This allows a user to change items in a PO, including:

  • Name

  • Description

  • Quantity

  • Rate

  • Tax

  • Discount

  • Shipping

This does not include the PO general ledger, which can be enabled using ‘Set PO’s General Ledger (154).’

Users who do not have this permission can still change the items of POs assigned to them if the PO is in set-up mode.

Dependencies: 'Edit and Complete My POs (#184)' or 'Edit and Complete Any POs (#185)' must be enabled for this permission to work.

Default Roles: Manager

Receive PO Items (#152)

What it does: This allows a user to receive items for a PO.

If this permission is disabled, they cannot initiate receipt of any items associated with a PO, with one exception: if a user is assigned to a task that includes a service PO item, the item will be marked as received once the task is completed.

Dependencies: None

Default Roles: Technician, Manager

Start Next PO Step For Others (#164)

What it does: This allows a user to start the next step of a PO.

The user will override this permission if the next step of the PO is assigned to them and the PO is in set-up mode.

Dependencies: None

Default Roles: Manager

Disapprove PO Step For Others (#165)

What it does: This allows a user to disapprove a PO, which sends the PO back to the most previous step.

Dependencies: None

Default Roles: Manager

Request Purchases (#175)

What it does: This allows a user to make a purchase request.

This permission is commonly given to users who should be able to request purchases through another user or team, such as a purchasing department or inventory manager, without being able to order items.

Dependencies: None

Default Roles: Technician, Manager

Disapprove Purchase Requests (#176)

What it does: This allows a user to disapprove a purchase request.

When a purchase request is made, a new PO will be created and assigned to the chosen default user for approval. A user with this permission can disapprove the request, which will close out the PO and send a notification to the original purchase requester that their request was not approved.

Dependencies: None

Default Roles: Manager

Export POs (#191)

What it does: This allows a user to export POs and PO items as a .csv file.

Dependencies: None

Default Roles: Manager, View Only

Click here to go back to the Table of Contents.

Bills

Included in this section (click on the permission to expand the description!):

View Manage Bills (#156)

What it does: This allows a user to change a bill’s transaction before marking it as paid. This can be used to adjust the amount of items received if the initial count has changed.

Dependencies: None

Default Roles: Manager, View Only

Change Bill Transaction (#158)

What it does: This allows a user to change a bill’s transaction before marking it as paid. This can be used to adjust the amount of items received if the initial count has changed.

Dependencies: None

Default Roles: Manager

Mark Bill as Paid (#157)

What it does: This allows a user to mark a bill as paid.

This is typically done after your accounting or finance department has paid the vendor associated with the bill. A PO will only fully close once all items are received and all associated bills are marked as paid.

Dependencies: None

Default Roles: Manager

Delete Bill (#159)

What it does: This allows a user to delete a bill.

Use caution when enabling this permission. Once a bill is deleted, it cannot be restored. Deleting a bill will result in the following:

  • Parts associated with the PO/bill will be removed from your parts inventory

  • Parts or services will be removed from their associated tasks as if they were never used

Users who do not have this permission can still delete POs assigned to them if the PO is in set-up mode.

Dependencies: None

Default Roles: Manager

Export Bills (#192)

What it does: This allows a user to export bills as a .csv file.

Dependencies: None

Default Roles: Manager, View Only

Click here to go back to the Table of Contents.

General Ledgers

Included in this section (click on the permission to expand the description!):

Set PO Item's General Ledger (#154)

What it does: This allows a user to add or change the general ledger associated with a PO item from existing options. This permission does not allow the user to create new general ledgers.

Users who do not have this permission can still set a general ledger on POs assigned to them if the PO is in set-up mode.

Dependencies: None

Default Roles: Manager

Add General Ledger (#153)

What it does: This allows a user to create new general ledgers and update existing general ledger names.

Dependencies: None

Default Roles: Manager

Delete General Ledger (#155)

What it does: This allows a user to delete a general ledger. Deleting a general ledger will remove it from any associated POs or PO items.

Use caution when enabling this permission. Once a general ledger is deleted, it cannot be restored.

Dependencies: None

Default Roles: Manager

Click here to go back to the Table of Contents.

Budgets

Included in this section (click on the permission to expand the description!):

View Manage Budgets (#160)

What it does: This allows a user to access the ‘Manage Budgets’ page and view all budgets.

If this permission is disabled, they can still preview a budget.

Dependencies: None

Default Roles: Manager, View Only

Add Budget (#161)

What it does: This allows a user to create a new budget.

Dependencies: None

Default Roles: Manager

Delete Budget (#162)

What it does: This allows a user to delete a budget. Deleting a budget will not delete it from any associated POs or PO items, but it will be removed from the list of available budgets for new POs.

Dependencies: None

Default Roles: Manager

Change Budget Settings (#163)

What it does: This allows a user to change budget settings, including:

  • Budget name

  • Default budget

  • How the PO workflow occurs

  • Spend limits

  • User access

Dependencies: None

Default Roles: Manager

Export Budgets (#193)

What it does: This allows a user to export budgets as a .csv file.

Dependencies: None

Default Roles: Manager, View Only

Click here to go back to the Table of Contents.

Users

Included in this section (click on the permission to expand the description!):

View Manage Users (#28)

What it does: This allows a user to access the ‘Manage Users’ page.

Use caution when enabling this permission: a user who has access to this page and its permissions may be able to change user passwords, wage and work hours, and roles within Limble.

Dependencies: None

Default Roles: Manager, View Only

Activate and Deactivate Users (#85)

What it does: This allows a user to mark other users as active or inactive.

When marked as inactive, a user can no longer use Limble. They will stay in your account for reporting purposes, but will not count towards the cost of your Limble subscription.

Dependencies: 'View Manage Users (#28)' must be enabled for this permission to work.

Default Roles: Manager

Change User Email and Push Notification Settings (#86)

What it does: This allows a user to change if other users receive emails, and push notifications on the mobile app.

Dependencies: 'View Manage Users (#28)' must be enabled for this permission to work.

Default Roles: Manager

Send Reset Password Email (#87)

What it does: This allows a user to send an email to another user to reset their password.

This permission does not allow the person with this role to reset another user’s password themselves - only Super Users can reset passwords on behalf of other users.

Dependencies: 'View Manage Users (#28)' must be enabled for this permission to work.

Default Roles: Manager

Change Users Email Address, First and Last Name, Phone Number (#88)

What it does: This allows a user to change the basic information of other users, including:

  • Name

  • Email address

  • Phone number

This does not include user logins.

Dependencies: 'View Manage Users (#28)' must be enabled for this permission to work.

Default Roles: Manager

View and Change Users Wage (#89)

What it does: This allows a user to view and change user wages.

Dependencies: 'View Manage Users (#28)' must be enabled for this permission to work.

Default Roles: Manager

View and Change Users Work Day Hours (#90)

What it does: This allows a user to view and change working hours for users.

This permission is helpful for scheduling purposes, so users are not assigned more work than they can complete in their allotted working hours.

Dependencies: 'View Manage Users (#28)' must be enabled for this permission to work.

Default Roles: Manager

Add or Remove Roles from Users (#91)

What it does: This allows a user to assign or remove roles from other users.

Dependencies: 'View Manage Users (#28)' must be enabled for this permission to work.

Default Roles: Manager

Add Users (#97)

What it does: This allows a user to add users to Limble.

Only Super Users can permanently delete a user.

Dependencies: 'View Manage Users (#28)' must be enabled for this permission to work.

Default Roles: Manager

Click here to go back to the Table of Contents.

Subscription

Included in this section (click on the permission to expand the description!):

View Subscription (#96)

What it does: This allows a user to access the ‘Your Limble Subscription’ page.

Use caution when enabling this permission: a user who has access to this page and its permissions may be able to make changes to your organization’s Limble account and subscription.

Dependencies: None

Default Roles: None - only Super Users can access this page by default.

Change Payment Method (#92)

What it does: This allows a user to add, change or update the payment method on file.

Dependencies: 'View Subscription (#96)' must be enabled for this permission to work.

Default Roles: None - only Super Users can access this page by default.

Change Plan (#93)

What it does: This allows a user to change your Limble plan.

Use caution when enabling this permission: changing your Limble plan may result in an increase to your current subscription rate.

Dependencies: 'View Subscription (#96)' must be enabled for this permission to work.

Default Roles: None - only Super Users can access this page by default.

Activate or Cancel Limble (#94)

What it does: This allows a user to activate or cancel your organization’s Limble account.

Use caution when enabling this permission! If you have questions or concerns about your Limble account, reach out to your dedicated Limble advisor.

Dependencies: 'View Subscription (#96)' must be enabled for this permission to work.

Default Roles: None - only Super Users can access this page by default.

View Invoices (#95)

What it does: This allows a user to view your organization’s Limble payment history.

Dependencies: 'View Subscription (#96)' must be enabled for this permission to work.

Default Roles: None - only Super Users can access this page by default.

Click here to go back to the Table of Contents.

Related Articles

Still don’t see what you’re looking for? Check out our YouTube channel for more tips and tricks! You can also reach out to us anytime at support@limblecmms.com.

Did this answer your question?