Overview
Locations are the core building blocks of Mobaro. Each Location represents a physical or functional space — a ride, stand, area, or team zone — where Checklists, Results, and Assignments take place. Once created, a Location can be configured with direct members, Location Groups, and optional settings like RideOps or operational logging. This article covers creating one and the settings available on it.
Users must be Super Users or have one of the following to create and edit Locations:
Locations: Create or Modify, or Organization: Administrate
Why this matters: Schedules, Assignments, Results, and reporting all hang off Locations. A clean, well-named Location set up correctly from the start saves significant rework later — see Location best practices before building out a large set.
Create a Location
Go to the Locations section
In the Mobaro Backend, go to Locations in the left-hand navigation.
Add a new Location
Click + Create in the top bar to open the Location editor panel on the right.
Fill in general information
Enter the Name of the Location. Optionally, add:
Email — for distributing reports through Notification Rules.
External ID — used in integrations and imports.
Language — overrides the default User language when viewing content at this Location.
Add direct memberships
In the Direct Memberships section, add:
Users — people directly assigned to the Location.
User Groups — teams associated with the Location.
Location Groups — broader clusters this Location belongs to (e.g. West Park).
Note: Membership is how Users get access to this Location. For the full picture of direct vs Group-based access, see Giving Users access to a Location.
Configure Location settings
Geographic location (optional)
Drop a GPS pin for the Location. Useful if you're using GPS validation on Checklists.
Operations (optional)
Enable Operational Logging if Users should log open/close status or downtime events manually. To measure downtime against real opening hours, also attach an opening-hours Calendar — see Add operating hours to a Location.
RideOps (optional, add-on)
Enable RideOps if this Location will be used in the RideOps app. This unlocks RideOps-specific configuration. The RideOps add-on package is required.
Scanner code (optional)
Set a custom Scanner Code or leave it blank to auto-generate one. Useful for QR-code access to the Location or for validation within Checklists.
Best practice: Tag the Location with Location Properties (ride type, equipment, area) so one Checklist can adapt across many Locations. See Creating and assigning Location Properties.
Frequently asked questions
Q: What's the difference between a Location and a Location Group?
A: A Location is an individual area (e.g. Roller Coaster A); a Location Group is a collection of Locations (e.g. Zone 1 — Coasters) used for organization, reporting, and access. See How to create Location Groups.
Q: Can I use a Location without adding Users or User Groups?
A: Yes, but no one will be able to access it in the mobile app until at least one User or Group is assigned — directly or through a Location Group.
Q: What does enabling RideOps do?
A: It makes the Location available in the RideOps mobile app, enabling dispatches, logs, and operator Checklists. The RideOps add-on package is required.
Q: Can I create many Locations at once?
A: Yes — via the Mobaro API, or a CSM-assisted CSV import. See Importing Locations via the Mobaro API (and CSV).