Overview
Location Groups are folders that organize your Locations. They can be flat or nested to mirror your park, resort, or facility structure, and they do real work beyond tidiness: grouping improves filtering across Dashboards and reporting, lets you assign one Checklist to many Locations at once, and — importantly — grants Location access at scale.
Users must be Super Users or have one of the following to create and edit Location Groups:
Location Groups: Create or Modify, or Organization: Administrate
Why this matters: A Location Group structure that mirrors your real-world zones becomes the backbone of access and reporting. Add a User or User Group to a group once, and they get access to every Location in it — including ones you add later. Get this structure right and most access management takes care of itself.
Create a Location Group
Open the Location Groups view
Go to Location Groups in the Mobaro sidebar. You'll see a folder structure showing any existing groups in your account.
Add a new group
Click + Create Location Group at the top of the panel.
Name the group something intuitive (e.g. Water Park or Food & Beverage).
(Optional) Add direct members — Users, User Groups, or Locations.
Nest or move Location Groups
To nest one group within another:
Select the group you want to move.
Click the move icon (folder with arrow).
Select the parent group from the list.
Click
Confirm.
This lets you build a full hierarchy (e.g. Amusement Park > Rides & Attractions > Coasters).
Add members to a Location Group
You can add:
Users — Users who should have access to every Location in this group.
User Groups — team-based access for assignment, notifications, or filtering.
Locations — assign existing Locations into this group.
Note: Adding a Location to a group is purely organizational — it does not affect whether the Location is active. Adding a User or User Group, however, grants them access to every Location in the group and its children. See Giving Users access to a Location.
Best practices
Match groups to your real-world zones (park areas, departments).
Nest deeper for large operations, but avoid over-nesting — three to four levels is usually plenty.
Keep naming consistent across groups and Locations. See Location best practices.
Frequently asked questions
Q: Does adding a User or User Group to a Location Group grant access to every Location inside it?
A: Yes. It grants access to all Locations within that group, as well as any nested child groups.
Q: Can I move a Location Group without losing data?
A: Yes. Moving a group doesn't delete or modify any data — it only changes the group's position in the structure. Be aware, though, that if the group is used in scheduling, moving it under a different parent may affect Schedules or Assignments tied to the previous structure.
Q: Should I create Location Groups before or after importing Locations?
A: Either works. Having the group structure ready before importing makes sorting Locations faster afterward.