Overview
Location Properties are tags that describe your Locations: ride type, equipment on site, park area, and so on. Each Property belongs to a Category, and a Location can have any number of Properties from any number of Categories.
Their main job is Checklist logic: one Checklist can show or hide questions depending on the Properties of the Location it's completed at. This article covers creating Categories and Properties, assigning them to Locations, and what happens when you change or delete them.
At a glance |
|
Who can do this | Categories and Properties: Super Users, or a Role with Organization › Administrate. Assigning them: Super Users, or a Role with Locations › Modify |
Where | Configuration › Locations › Location Properties; Locations › a Location › Edit › Location properties |
Works on | Backend (web). Property-based Checklist logic applies wherever the Checklist is completed. |
Availability | All organizations |
💡 Why this matters: Without Properties, every variation in your operation needs its own Checklist. With them, one Checklist adapts: track questions appear only on coasters, water-quality questions only on water rides. Less duplication, and fewer Checklists drifting out of sync.
Categories and Properties
Object | What it is | Example |
Category | A group of related Properties. Use one Category per kind of attribute. | Ride Type, Equipment, Park Area |
Property | A tag within a Category that you assign to one or more Locations. | Under Ride Type: Coaster, Flat Ride, Water Ride |
A Location can hold Properties from several Categories, for example Ride Type: Coaster and Park Area: North. Mobaro doesn't limit a Location to one Property per Category.
Create Categories and Properties
1. Open the Locations configuration
In the Mobaro Backend, go to Configuration and select the Locations tab. Categories and Properties are managed in the Location Properties panel.
2. Add a category
Click Add category and enter a name, for example Ride Type.
3. Add properties
In the new Category, click the + button (Add property) and enter a Property name, for example Coaster. Repeat for each Property. Every Category and Property needs a name.
4. Save
Click the save icon (Save) at the top of the Location Properties panel. Mobaro confirms with Location properties were saved.
Assign Properties to a Location
1. Open the Location editor
Go to Locations, select the Location and click Edit.
2. Choose the Properties
In the Location properties section, select the Properties that apply to this Location. The section only appears once your organization has at least one Property.
3. Save the Location
Click Save. The change applies straight away.
🛑 Critical: Property changes take effect immediately and change which questions appear on that Location's Checklists. Removing a Property can hide questions that were shown before, including safety checks; adding one can show new ones. Review the affected Checklists before changing Properties on Locations in operation.
Rename or delete Properties
Rename a Category or Property by editing its name in the Location Properties panel and saving. It stays assigned to the same Locations.
To delete, click the × next to the Property (Delete property) or Category (Delete category), confirm, then save. Deleting a Category deletes all of its Properties.
🛑 Critical: Deleting a Property or Category can't be undone. As the confirmation says, Locations with the Property have it deleted, and Logic items with this property will be deleted from your Checklists. Note which Checklists use the Property before you delete it.
Where Location Properties are used
Checklist logic: show questions or sections only when the Location has, or doesn't have, a Property. See Logic based on a Location property.
Location records: the Location editor lists the Location's Properties under Location properties.
For background on how Properties fit into your Location setup, see Understanding Location Properties.
Example: one Checklist for four ride types
A park runs one Pre-Opening Inspection Checklist on every ride. Operators answer N/A to dozens of questions that don't apply, and maintenance can't tell what was actually checked.
Create a Ride Type Category with Coaster, Flat Ride, Water Ride and Kiddie Ride.
Tag each ride Location with its type in Location properties.
Add Property logic to the Checklist: track questions only for Coaster, water chemistry only for Water Ride, height-sign checks only for Kiddie Ride.
Result: each ride sees only its own questions, and a new ride is onboarded by tagging its Location, with no Checklist changes.
Best practices
Use clear, unabbreviated names everyone reads the same way: Coaster, not RC; Climbing Wall, not CW.
Keep each Category to one kind of attribute, such as ride type, area or equipment.
Before removing a Property from a Location or deleting it, check which Checklists use it in their logic.
Frequently asked questions
How do I show certain questions only at certain locations?
Tag those Locations with a Location Property, then add logic to the question or section based on that property in the Checklist editor. See Logic based on a Location property.
What categories can I create for location properties?
Any you like. Categories and Properties are free-text names you define, such as Ride Type, Park Area or No. of bedrooms. Keep each Category to one kind of attribute.
Can I bulk change location properties?
No. Bulk edit on the Locations page covers Operational Logging, Language and Radius only. Set properties on each Location in its editor, under Location properties.
Can I rename or delete a property after locations use it?
Yes. Renaming keeps it assigned everywhere. Deleting can't be undone: it removes the property from every Location and deletes the Checklist logic items that use it. Check your Checklists first.
Can two categories use the same property name?
Yes. Mobaro doesn't require property names to be unique, so Small can exist under both Pool Size and Ride Size. Pick names that stay clear when you see them in Checklist logic.


