Overview
Location Groups are folders for your Locations. They can be flat or nested to mirror your park, resort or facility, and they do real work: Schedules can target a whole group, Dashboards and reports can filter by group, and members of a group get access to every Location in it.
This article covers creating a Location Group, nesting groups, adding members, and deleting a group.
At a glance |
|
Who can do this | Super Users, or a Role with Location Groups › Create (new groups), Modify (existing groups) or Delete. Creators can modify and delete their own groups. |
Where | Location Groups in the Backend menu |
Works on | Backend (web). Access granted by a group applies in the mobile app and RideOps. |
Availability | All organizations |
💡 Why this matters: A group structure that mirrors your real zones becomes the backbone of access and reporting. Add a User or User Group to a group once and they can see every Location in it, including ones you add later.
Create a Location Group
1. Open Location Groups
Go to Location Groups in the Backend menu. The panel shows your existing groups as a tree.
2. Create the group
Click the + button (Create Location Group). If a group is selected in the tree, the new group is created inside it; otherwise it's created at the top level.
3. Name it and add members
Enter a Name, for example Water Park. Optionally, add Users, User Groups and Locations under Direct Memberships. Super Users also see an External ID field for integrations. Click Save.
Nest or move a Location Group
To put a group inside another group, or move it elsewhere in the tree:
Select the group in the tree.
Click the Move button (four-way arrow).
In Move Location Group, select the group that will become the new parent.
Click Confirm.
You can't move a group into itself or into one of its own child groups. Build as many levels as you need, for example Amusement Park › Rides & Attractions › Coasters.
Location Group members
A Location Group's Direct Memberships has three parts:
Users: get access to every Location in the group and its child groups.
User Groups: every member of the User Group gets that same access.
Locations: the Locations that belong to the group. Adding a Location doesn't change its settings, but the group's Users and User Groups (including those inherited from parent groups) get access to it.
Members are inherited downwards: child groups and their Locations show them under Inherited Memberships. Access is additive, so a user can see a Location if they're a member of it directly, through a User Group, or through any Location Group that contains it. They don't need all of these. See Giving Users access to a Location.
ℹ️ Note: Scheduling a Checklist on a Location doesn't give anyone access to it. Users only see the Checklist in the app if they can see the Location through one of the membership routes above.
Delete a Location Group
Select the group and click the trash button (Delete). The Locations inside aren't deleted; they're only removed from the group.
🛑 Critical: Deleting a Location Group can't be undone, and it also deletes all of its child groups. Schedules that target the group are updated, and users who had access only through the group lose it. Move child groups you want to keep before you delete.
Best practices
Match groups to your real-world zones, such as park areas or departments.
Nest deeper for large operations, but three to four levels is usually enough.
Grant access with User Groups on Location Groups rather than adding people to Locations one by one.
Keep naming consistent across groups and Locations. See Location best practices.
Frequently asked questions
How do I add a location to a location group?
Select the group in Location Groups and add the Location under Direct Memberships › Locations, then click Save. You can add several Locations at once. Or edit the Location and add the group under its Direct Memberships.
If I give a user group a location group, do I also need to add it to each location?
No. A User Group that's a member of a Location Group gets access to every Location in that group and in its child groups, including Locations added later.
Why can't a user see a location or its scheduled checklists?
The user isn't a member of that Location through any route: directly, through a User Group, or through a Location Group. Any one route is enough. Scheduling a Checklist doesn't grant access on its own. See Giving Users access to a Location.
What's the difference between a location and a location group?
A Location is one place where work happens, such as a ride. A Location Group is a folder of Locations used for access, scheduling and reporting. See Overview of locations in Mobaro.
Should I create locations or location groups first?
Either works. Creating the group structure first makes it quicker to sort new Locations into groups as you create them.