Overview
Two separate things decide what a User sees of your Locations: their Location membership and the Locations and Location Groups permissions on their Roles. This article explains those Role permissions, especially Locations › View: what it shows, what it doesn't, and when to use it.
To make someone a member of a Location, see Giving Users access to a Location. For the full access model, see How access works in Mobaro.
At a glance |
|
Who can do this | Super Users, or a Role with Roles › Create or Modify, can set these permissions |
Where | Administrate › Roles › a Role › Locations and Location Groups |
Works on | Backend (web) |
Availability | All organizations |
💡 Why this matters: Locations › View is often ticked as a quick fix when someone "can't see the ride". It doesn't fix that: it shows every Location's record and status, but no Results, Assignments or Notes. Making the User a member does.
Location permissions on a Role
Permission | What it allows |
Locations › View | See every Location and its Assets, in lists, pickers and Location widgets on dashboards. It doesn't make the User a member. |
Locations › Create | Create Locations. Implies View, Modify and Delete for Locations they created. |
Locations › Modify | Edit any Location, including its Direct Memberships. |
Locations › Delete | Delete any Location. |
Location Groups › View | See every Location Group. It doesn't make the User a member of the groups or their Locations. |
Location Groups › Create / Modify / Delete | Manage Location Groups, including which Locations, Users and User Groups they contain. |
Assets › Administrate | Manage Assets, only at Locations where the User is a member. |
Deleting a Location Group also deletes its sub-groups. See How to create Location Groups.
What Locations › View shows
Without Locations › View, a User sees only the Locations they're a member of, Locations they created, and Locations they operate in RideOps. With it, they see every Location in the organization:
In Locations and in Location pickers across the Backend.
In the Assets list.
In Location widgets on dashboards, such as the Location Overview, readiness, operational status, Downtime and MTTR/MTBF widgets.
Permissions that act on a Location also work at every Location the User can see. For example, a Role with Locations › View and Operations › Manage Downtime can edit and close Downtime at any Location, although the Downtime page still lists only Downtime at Locations they're a member of.
🛑 Critical: Locations › View shows every Location's records, Assets and operational status, including Downtime details in dashboard widgets. Give it only to people who need an organization-wide view, and review it during access audits.
What Locations › View doesn't show
Results, Assignments, Notes, Gallery images and the Downtime page show only for Locations the User is a member of, whatever their Role. Locations › View doesn't change that, and it doesn't add Checklists to the Mobaro app. Location Groups › View doesn't either.
It also doesn't let the User edit anything. What they can do comes from the other permissions on their Roles.
Permissions that change membership
⚠️ Heads-up: Locations › Modify and Location Groups › Modify let someone change who is a member of a Location, including adding themselves. That gives them access to the Location's Results, Assignments and Notes. Give these permissions only to people who manage access.
When to use Locations › View
People who set up Locations, Location Groups or Assets for the whole organization.
Managers who need an organization-wide status overview on dashboards. To see Results and Assignments too, also make them members of those Locations.
For everyone else, give access through membership, ideally through a User Group or Location Group.
Best practices
Use Location membership, not Locations › View, to give someone a Location's data.
Keep Locations › Modify and Location Groups › Modify to the few people who manage access.
Review who holds Locations › View and Location Groups › View during access audits.
Frequently asked questions
I gave a user View Locations and View Notes, but they still can't see all notes. Why?
Notes show only for Locations the User is a member of. Locations › View doesn't make them a member. Add the User, or a User Group they're in, to those Locations or to a Location Group that contains them.
Why does my Location Overview show the whole company instead of my own locations?
Your Role probably has Locations › View, or you're a Super User. Location widgets then include every Location. Without it, they show only Locations you're a member of.
How can a manager see all assignments at a location, not just ones assigned to them?
Give them a Role with Assignments › View and make them a member of that Location. Locations › View alone doesn't show Assignments. See the Role permissions reference.
How do I let someone create locations?
Give them a Role with Locations › Create. They can then view, edit and delete the Locations they create. To edit other Locations, they also need Locations › Modify.