Overview
Every Asset in Mobaro is scoped to a Location. The link between Asset and Location is what makes Asset-driven workflows possible — it's how Schedules know where to publish, how Assignments find their context, and how Users see only the Assets relevant to where they work.
Why this matters: Assets without correct Location linkage become invisible — Users in the right Location can't see them, Schedules don't fire, and Assignments can't be created against them. Getting the linkage right at creation prevents the most common Asset support issue: "the Asset exists but no one can find it."
Required access: To link Assets to Locations or modify the linkage, you must be a Super User or hold a Role with the Locations: Modify permission.
How the link between Assets and Locations works
When an Asset is created, it is assigned to a Location. From that point on:
The Asset inherits the access scope of its Location. Users with access to the Location can see and interact with the Asset; Users without access cannot.
The Asset becomes a valid Schedule Target and Assignment Target for that Location.
The Asset appears in Reports, Dashboards, and Gallery filters that are scoped to the Location.
Note: Asset-to-Location is a hard scoping relationship. If a User cannot access a Location, they cannot see or interact with any Asset on that Location, regardless of any other settings.
Create an Asset already linked to a Location
The cleanest way to link an Asset to a Location is to set the linkage at creation time. Two paths into the create flow are available, and both end in the same Asset record.
From the Location
When the Location is the starting point — for example, when standing up Assets for a new ride or facility:
From the Mobaro Backend, navigate to Locations.
Select the Location.
Click the
Assetsbutton.Click
+ Create.Fill in the Asset details and click
Save.
The new Asset is automatically linked to the Location you opened it from. No additional linkage step is required.
From the Assets tab
When you're creating multiple Assets across several Locations — for example, when bulk-onboarding Assets at the start of a season:
From the Mobaro Backend, navigate to Locations > Assets.
Click
+ Create.Select the target Location.
Fill in the Asset details and click
Save.
See also: Creating an Asset covers the underlying create flow in more detail, including field-level guidance.
One Asset, one Location
An Asset belongs to exactly one Location at a time. This is intentional — it gives every Asset a clear "home" for access, reporting, and routing purposes. If you need an Asset to exist in multiple physical contexts:
For shared Assets that genuinely move (a portable piece of equipment, a roving inspection vehicle), pick the Location that represents the Asset's home base, and rely on Location Groups or Locations with broader access scope to make the Asset visible to the relevant teams.
For Assets that need to be inspected from multiple locations (a single piece of equipment serving several zones), see moving an Asset between Locations below for how to handle the move when ownership genuinely shifts.
For "the same kind of Asset" that exists in multiple Locations (every restroom has a soap dispenser), create a separate Asset for each Location — they're distinct physical things and Mobaro treats them that way.
Best practice: Resist the urge to use one Asset record for many physical objects. Each physical Asset deserves its own record so its history, Assignments, and inspection results stay attached to that specific item. Mobaro is designed for this — there is no per-Asset cost.
Moving an Asset between Locations
When an Asset's Location ownership genuinely changes — a piece of equipment moves to a different ride, a tool is reassigned to a different shop — update the Location linkage to reflect the new home.
Update an Asset's Location
Navigate to Locations > Assets.
Search for and select the Asset.
Edit the Location field to point to the new Location.
Click
Save.
Watch out: Moving an Asset to a new Location changes who can see and interact with it. Users who had access via the old Location lose access; Users at the new Location gain access. Active Schedules and Assignments targeting the Asset may need to be update and visibility shifts to whoever has access to the new Location.
Note: Historical Results, completed Assignments, and audit log entries on the Asset are not affected by a Location change. Past activity stays attached to the Asset and continues to appear in reporting with original attribution.
Auditing Asset–Location linkage
Periodic audits of Asset-to-Location mapping catch problems before they generate support tickets:
Orphaned-feeling Assets — Assets whose Location is no longer operational. Either move the Asset or archive it.
Misfiled Assets — physical Assets that were created on the wrong Location during onboarding. Common at scale; usually surfaces when a Schedule fires but no one finds the work in their queue.
Duplicate Assets — the same physical Asset created twice, once per Location. Pick the canonical record, move it to the right Location, and delete the duplicate.
Best practice: Audit Asset-to-Location mapping at the start of each operating season. A 30-minute pass through the Assets list at the right time of year prevents recurring "Asset not visible" support escalations once the season is in full swing.
Troubleshooting
A User can't see an Asset they expect to see
Check the following in order:
Confirm the Asset exists and was saved successfully — search for it in Locations > Assets.
Confirm the Asset's Location field points where you expect.
Confirm the User has access to that Location, either directly or via a User Group.
Confirm the User's Role grants the relevant Location-scoped permission (View, Modify, etc.) for the operation they are trying to perform.
A Schedule targeting an Asset isn't firing for the expected Users
Schedule visibility flows through the Asset's Location. If Users at the Asset's Location can't see the Schedule, they will not see Checklists triggered by it. Confirm the Asset, the Location, and the Assignees on the Schedule are all aligned.
See also: Asset-driven Assignments and Schedules covers Asset-targeted Schedule and Assignment workflows in detail, including assignee visibility.
See also
Creating an Asset — the create flow this article references.
Asset-driven Assignments and Schedules — for using linked Assets as Schedule and Assignment targets.
Organizing Assets at scale — for naming conventions, Location Groups, and patterns when managing many Assets.
How to create Locations — for the Location side of the linkage.
How to create Location Groups — for scoping access across multiple Locations at once.
Frequently asked questions
Q: Can an Asset belong to more than one Location?
A: No. An Asset belongs to exactly one Location at a time. To make an Asset visible to teams at multiple Locations, use Location Groups or broader Location access via User Groups.
Q: What happens to historical Results when I move an Asset to a new Location?
A: Historical Results stay attached to the Asset and continue to appear in reporting. The move does not retroactively reassign past activity to the new Location.
Q: Can I create the same Asset on multiple Locations?
A: Yes — but each one is a separate Asset record with its own history. This is the right pattern when the Assets are physically distinct (one soap dispenser per restroom). It's not the right pattern for a single physical Asset that needs to be visible to multiple teams.
Q: If I delete a Location, what happens to its Assets?
A: Assets attached to a deleted Location lose their primary scope. Move Assets to another Location before deleting the Location to preserve their access and reporting context.
Q: Do Assets inherit Location Properties?
A: Yes, assets do inherit Location Property values directly.
Q: Can I bulk-move multiple Assets to a different Location?
A: There is no native bulk-move action for Assets. For large reorganizations, the Mobaro API can update Location linkage on Assets programmatically. For small batches, edit each Asset individually.