Overview
In Mobaro, Locations are the foundation of how you organize your operation. A Location can be anything you manage, inspect or monitor: an attraction, a shop, a food outlet, a pool, or a back-of-house area.
Checklists, Schedules, Assignments and reporting are all organized around Locations, so a clean Location setup keeps your data accurate and easy to read. This article explains the concepts and links to the how-to articles for each part.
At a glance |
|
Who can do this | Everyone sees the Locations they're a member of. Creating Locations: Super Users, or a Role with Locations › Create |
Where | Locations, Location Groups and Configuration › Locations |
Works on | Backend (web), Mobile app, RideOps, Public API |
Availability | All organizations |
💡 Why this matters: Think of Locations as the map of your operation in Mobaro. The clearer the map, the easier it is for staff to find the right Checklist in the right place, and for managers to compare results across sites.
What a Location does
A Location is:
Where work happens. Checklists are completed at a Location, and each Result records it.
What Schedules target. A Schedule sets when a Checklist is due at its Locations and how often it repeats.
Usually where Assignments point. Most Assignments target a Location, but an Assignment can target a User instead.
A unit of access. In the mobile app, users see a Location and its Checklists only if they're a member of it. In the Backend, Super Users and Roles with Locations › View can see every Location.
A unit of reporting. Dashboards and reports can filter and compare by Location or Location Group.
A readiness signal. Each Location shows whether it's ready for operation. See Configuring readiness colors on the Location Overview.
What's on a Location
Every Location has a Name. Everything else is optional:
Setting | What it's for |
Email, External ID, Language | Contact address, an identifier for integrations (Super Users only), and the language for RideOps content. |
Opening Hours, Time zone | Measure uptime against real opening hours. See Add opening hours to a Location. |
Direct Memberships | The Users, User Groups and Location Groups linked to the Location. |
Geographic Location | Address and radius, used to check that Checklists are answered on site. |
Operations, RideOps | Operational logging (open, close, Downtime) and use in the RideOps app. |
Scanner Code | The code behind the Location's QR code. |
Location properties | Tags that drive Checklist logic. |
For the step-by-step setup and the rules for each field, see How to create locations.
Location Groups and hierarchy
Location Groups are folders of Locations. Groups can be nested inside other groups to mirror your parks, sites or zones, for example Resort › Water Park › Slides. Locations themselves aren't nested inside each other; they sit in one or more groups.
Groups save work in three ways: a Schedule can target a whole group, Dashboards can filter by group, and adding a User or User Group to a group gives them access to every Location in it and its child groups. See How to create location groups.
Properties and Assets
Location Properties describe a Location, such as ride type or equipment, so one Checklist can adapt to each Location. See Creating and assigning Location Properties.
Assets are the equipment at a Location, such as a train or a pump, organized in a tree under it. See Linking Assets to Locations.
Best practices
Use clear, descriptive names so staff know immediately where to perform checks.
Represent each physical area once. Duplicate Locations split your history and reporting.
Organize Locations into Location Groups to simplify access, scheduling and reporting.
Review your Location list regularly. Deleting a Location can't be undone, so rename or reschedule where you can.
Frequently asked questions
How do I link a checklist to a location?
Through a Schedule. Create a Schedule for the Checklist and choose the Location, or a Location Group, as its target. Members of the Location then see the Checklist in the app. See How to schedule a Checklist.
Can I use the same checklist at multiple locations?
Yes. You don't need a copy per Location. Target one Schedule at several Locations or at a Location Group, and each Location gets its own Checklist to complete.
Should I create a new location for every checklist?
No. Create one Location per real place, such as a ride or shop, and schedule as many Checklists on it as you need. Use Location Properties when one Checklist should vary between Locations.
Can I rename a location later?
Yes. Edit the Location and change its Name. Schedules, Assignments and Results stay linked, because they point to the Location itself, not to its name.
How do I move a checklist from one location to another?
Change the targets of the Schedule that creates it. To move a Result that was already recorded at the wrong Location, see Changing a result's location.