Overview
Locations are the building blocks of Mobaro. Each Location is a physical or functional place, such as a ride, shop, pool or back-of-house area, where Checklists are completed and Assignments are carried out.
This article walks through creating a Location and every setting in the Location editor, including the ones with rules you might trip over. For what Locations are and how they relate to groups, Schedules and reporting, see Overview of locations in Mobaro.
At a glance |
|
Who can do this | Super Users, or a Role with Locations › Create. Editing and deleting need Locations › Modify or Delete; creators can edit and delete their own. External ID: Super Users only. |
Where | Locations › Create |
Works on | Backend (web). Locations can also be created through the Public API. |
Availability | All organizations |
💡 Why this matters: Schedules, Assignments, Results and reporting all hang off Locations. A clearly named Location with the right members and settings from day one saves rework later. See Location best practices before building a large set.
Create a Location
1. Open Locations
In the Mobaro Backend, go to Locations in the menu.
2. Click Create
Click Create in the toolbar. The Location Editor opens on the right.
3. Fill in General Information
Enter the Name (required). The other fields are optional:
Email: a contact address for the Location. It must be a valid email address.
External ID: an identifier for integrations and imports. Only Super Users can set it.
Language: the language used for this Location's content in RideOps. If empty, the organization's default language is used.
Opening Hours and Time zone: attach one opening-hours Calendar to measure uptime against real opening hours. Once you choose one, Time zone becomes required. See Add opening hours to a Location.
4. Add Direct Memberships
Under Direct Memberships, add the Users and User Groups who should see this Location, and the Location Groups it belongs to. Members of those Location Groups get access too. See Giving Users access to a Location.
5. Set the optional settings
Set any of the settings described below, then click Save.
Optional Location settings
Section | What it does |
Geographic Location | Pin the Location's address on a map and set a radius. Used to check whether a Checklist was answered at the correct location. |
Operations | Enable Operational Logging lets you log open and close times, including Downtime, for this Location. |
RideOps | Enable RideOps lets operators use the Location in the RideOps app. Then fill in RideOps Settings. If you're unsure whether RideOps is included in your agreement, ask your CSM. See Setting up RideOps. |
Scanner Code | A custom code for the Location's QR code. Leave it empty to generate one automatically. |
Location properties | Tags that drive Checklist logic. Shown once your organization has Properties. See Creating and assigning Location Properties. |
⚠️ Heads-up: Enable RideOps stays greyed out until Enable Operational Logging is ticked. Turning Operational Logging off later also turns RideOps off and closes the Location if it's open. Ticking Enable RideOps opens RideOps Settings; if you close it without the required dispatch values, RideOps is unticked again.
A custom Scanner Code must be unique across all your Locations and Assets, and can't start with locations or assets. Mobaro shows Scanner code is already in use if it's taken. To print codes for several Locations, select them on the Locations page and use Export Scanner Codes.
Delete a Location
On the Locations page, select one or more Locations and click Delete. Schedules and Location Groups that include them are updated to remove them.
🛑 Critical: Deleting a Location can't be undone, and there's no archive option. Assets at the Location aren't moved or deleted, so move them to another Location first. If you only want to stop using a Location, remove its Schedules instead.
Best practices
Tag each Location with Location Properties (ride type, equipment, area) so one Checklist can adapt across many Locations.
Grant access through Location Groups and User Groups rather than adding people to each Location.
Decide on a naming pattern before you create many Locations, and use External ID for codes from other systems rather than putting them in the name.
Frequently asked questions
How do I add a new location to my Location Overview?
Make sure you're a member of the Location, then check the Location Overview widget's location filter: if it's limited to specific Locations or Location Groups, add the new one. See Location Overview Widget.
Why is the External ID field greyed out?
Only Super Users can set or change a Location's External ID. For other users the field is read-only. External ID is an identifier for integrations and imports, and you can search Locations by it.
Why isn't my new location showing in the app or RideOps?
App users see only Locations they belong to: add them in Direct Memberships or via a group. For RideOps, tick Enable Operational Logging and Enable RideOps, then complete RideOps Settings. If the tablet's RideOps Key is limited to locations, add it. See Setting up RideOps.
Can we delete or merge locations?
You can delete: select the Location on the Locations page and click Delete. It can't be undone. There's no merge. To combine two, move Schedules and Assets to the one you keep, then delete the other.
Can I create many locations at once?
Yes, through the Mobaro API, or ask Mobaro to import them from an Excel workbook with the columns Name, Email, Externalid and OperationalLogging. See Importing Locations via the Mobaro API (and CSV).