Overview
Location Properties are tags that describe your Locations: ride type, equipment on site, park area, regulatory category. Each Property sits in a Category, and a Location can hold any number of Properties from any number of Categories.
Their job is to let one Checklist adapt to where it is completed. Checklist logic can show or hide questions and pages depending on the Properties of the Location, so you maintain one Checklist instead of a copy per ride type. This article explains how Properties work and how to plan them. For the setup steps, see Creating and assigning Location Properties; for the Checklist side, see Logic based on a Location property.
At a glance |
|
Who can do this | Categories and Properties: Super Users, or a Role with Organization › Administrate. Assigning them to Locations: Super Users, or a Role with Locations › Modify |
Where | Configuration › Locations › Location Properties; Locations › a Location › Location properties |
Works on | Backend (web) to set up; the logic applies in the Mobile app and RideOps. Also Public API |
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. Fewer Checklists means fewer versions 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 Locations. | Coaster, Flat Ride, Water Ride |
Names are free text that you choose. Every Property needs a name, and names don't have to be unique, so Small can exist under both Pool Size and Ride Size. A Location can carry several Properties from the same Category.
How Property logic works
You add logic to a question, element or page in the Checklist editor and choose Based on a property. The condition checks the Properties of the Location the Checklist is being completed at. Pick one or more Properties and a comparison: contains any, contains all, does not contain any or does not contain all. See Logic based on a Location property for the steps.
Which Location counts. The one the Checklist is completed for, which is also the Location recorded on the Result.
No Properties on a Location. Content that requires a Property stays hidden there; content that requires the Location not to have a Property shows. Content without Property logic always shows.
Completed Results don't change. Adding or removing Properties affects Checklists completed afterwards, not Results already recorded.
🛑 Critical: Property changes apply to every Checklist that uses them. Removing a Property from a Location can hide questions that were shown before, including safety checks, and deleting a Property or Category also deletes the Checklist logic items that use it. This can't be undone. Check which Checklists use a Property before you change or delete it.
Where Properties show up
Place | What happens |
Checklist logic | Shows or hides content per Location. This is the main use. |
Location editor | Lists the Location's Properties under Location properties. The section appears once your organization has at least one Property. |
Public API and webhooks | The API can create, update and delete Properties and set them on Locations. Location webhooks include the Location's Properties. See Getting started with the Mobaro API. |
Copying a Checklist to another organization | Logic based on Location Properties isn't copied, because Properties belong to one organization. |
Properties aren't a reporting filter: the Locations page has no Property filter or column, and editing several Locations at once (Edit multiple locations) covers only Operational Logging, Language and Radius. Set Properties on each Location in its editor, or through the API for large numbers.
Plan your Properties
Example: one inspection for four ride types. A park runs one pre-opening Checklist on every ride. Create a Ride Type Category with Coaster, Flat Ride, Water Ride and Kiddie Ride, and tag each ride. Show track questions only for Coaster, water chemistry only for Water Ride. A new ride is onboarded by tagging its Location, with no Checklist changes.
Example: questions that build up. For units with one to four bedrooms, tag each Location with its size (1 bed to 4 bed). Show the Bedroom 3 questions when the Location has any of 3 bed or 4 bed, and Bedroom 4 only for 4 bed.
Best practices
Keep each Category to one kind of attribute, such as ride type, area or equipment.
Use clear, unabbreviated names everyone reads the same way: Coaster, not RC.
Tag every Location in a group consistently, so a missing tag doesn't silently hide a question.
Before removing or deleting a Property, check which Checklists use it in their logic.
Frequently asked questions
How do I hide a question at certain locations or areas?
Tag the Locations with a Location Property, then add logic Based on a property to the question or page in the Checklist editor. You don't need a separate Checklist. See Logic based on a Location property.
A question still shows at a location where it shouldn't. Why?
Check three things: the Location's Properties in its editor, the comparison (contains any, contains all, does not contain any or does not contain all), and which Location the Checklist was completed for. Content without Property logic always shows.
Can one question show for several property values?
Yes. Pick several Properties in one condition and choose contains any, for example 3 bed or 4 bed. Use contains all only when a Location must carry every Property.
Can I see which locations have a certain property?
Not as a list. The Locations page has no Property filter. Open each Location's editor, or list Locations with their Properties through the Mobaro API.
What happens if I remove a property from a location?
Checklists completed there afterwards follow the new Properties: content that required the Property is hidden, and content that required it to be absent now shows. Results already recorded don't change.