Skip to main content
Location Based Permissions for Users in UpKeep

Learn how to set location based permissions so that your users can only see certain locations and the attributes tied to those locations.

Updated over a month ago

Available On: Starter, Professional and Business Plus


Location-Based Permissions let users access UpKeep with a single email, but their view is tailored to their specific locations. Users may have access to one, multiple, or all locations, depending on their role. It's important to ensure users are appropriately assigned to relevant location(s) to align with their visibility and responsibilities. 🌐👥🔍



How to Enable Locations Based Permissions

⚠︎ You must be an administrator to set location based permissions for users.

Note: Location Based Permissions are set at the parent location level. The parent location and all sublocations will be visible to the user when a parent location is selected.

  1. Log into UpKeep and navigate to People and Teams

  2. Locate the user via email or name

  3. Click on the user and select Edit

  4. Scroll down and select Is Location Based

  5. Select locations the user should see and click Save

  6. Now, when this user logs in the next time, they will ONLY be able to see the LOCATIONS you have selected for them to see.


How to Disable Location Based Permissions

Log into UpKeep and navigate to People and Teams

  1. Locate the user via email or name

  2. Click the user's name and select Edit

  3. Scroll down and deselect Is Location Based. Be sure to click save!

⚠︎ When toggled OFF, users can see all Locations and attributes tied to them


What all can a user see when Location Based Permissions are turned on?

Users see only the following data objects with a location assignment relevant to their location.

  • Parts

    • Parts/Inventory module

    • Web: Counts on Parts/Inventory for items that need action (i.e. Parts running low or out of stock) respects user’s location access

    • Parts on Work Orders view, edit, and creation

      • This includes hiding parts and associated costs even if added to the work order

    • Parts on Assets view, edit, and creation

    • Parts on Purchase Orders creation and edit

      • Already created purchase orders with parts for other locations are still visible and the parts on them are all visible

    • Parts on PM Triggers edit and creation

    • You can still create parts for other locations, but they will not be visible after creation

  • Assets

    • Assets module

    • Assets on Work Orders view, edit, and creation

    • Assets on requests edit and creation

    • Assets on PM Triggers edit and creation

    • Assets on Meters edit and creation

    • You can still create assets for other locations, but they will not be visible after creation

  • Work Orders view

    • Work Orders module

    • You can still create work orders for other locations, but they will not be visible after creation

  • Meters view

    • Meters module

    • You can still create meters for other locations, but they will not be visible after creation

  • Locations

    • Locations module

    • Locations on Work Orders edit and creation

    • Locations on Assets edit and creation

    • Locations on Requests edit and creation

    • Locations on PM Triggers edit and creation

    • Locations on Meters edit and creation

    • Locations on Parts edit and creation

  • Requests

    • As mentioned above, when adding assets and locations to a new or existing request the dropdown list will be restricted based on what locations the user has access to

    • Web counts in the left nav and what requests are visible are not affected by location access


FAQ about Locations Based Permissions

Does this affect notifications?

Location based users will receive notifications for request and work orders they have been given permission to in UpKeep based on their role. Admins + Limited Admins will receive work request and work order notifications, while Technicians + Limited Technicians will only be notified of work orders they are assigned to.

Does this filter down what locations can be selected in requests?

Yes

Can admins change their own location permissions?

Yes

Does this affect the “action needed” counts in blue bubbles in the left navigation on the web application?

No, those action item counts will still be looking at all entities across the org regardless of permissions

Are analytics and reports restricted by this?

Yes, Location Based Permission will be respected in analytics.

Did this answer your question?