Overview
Every Asset in Mobaro belongs to one Location — directly, or under a parent Asset at that Location. The Location decides who can see the Asset and where work targeted at it shows up, so getting it right is what makes asset-driven Schedules and Assignments work.
This article covers how the link works, creating an Asset at the right Location, and moving Assets between Locations. For the create form itself, see Create an Asset.
At a glance |
|
Who can do this | Super Users, or a Role with Assets › Administrate — at Locations where you're a member. Moving needs this at both the old and the new Location. |
Where | Locations › Assets, or Locations › select a Location › Assets |
Works on | Backend (web). Moves are also possible through the Public API. |
Availability | All organizations |
💡 Why this matters: An Asset at the wrong Location is invisible to the people who need it and brings its work with it — Checklists and Assignments end up with the wrong team. Setting the Location right at creation prevents the most common Asset question: "the Asset exists, but nobody can find it."
How the Location link works
Visibility — an Asset is visible to Super Users and to members of its Location, whether they're members directly, through a User Group or through a Location Group. See Giving Users access to a Location.
Management — creating, editing and moving Assets needs Assets › Administrate; without Super User access, it only applies at Locations where you're a member.
Work — asset-driven Schedules and Assignments reach the people with access to the Asset's Location, and Results and Assignments can be filtered by Asset. See Asset-driven Assignments and Schedules.
Location Properties — Assets don't have Location Properties of their own. When a Checklist runs against an Asset, its logic uses the Properties of the Asset's Location. See Understanding Location Properties.
Create an Asset at a Location
You set an Asset's Location when you create it. It can't be changed in the Asset's edit form afterwards — only with Move.
1. From the Location
Go to Locations, select the Location and click Assets. Click Create, fill in the details and save. The new Asset belongs to that Location. This is quickest when you're setting up the Assets of one ride or facility.
2. From the Assets list
Go to Locations › Assets and click Create. In Create asset, select the Location that will be the Asset's parent and, if needed, a parent Asset under it (see Asset hierarchies and parent/child relationships). Fill in the details and save. This suits onboarding Assets across several Locations.
One Asset, one Location
An Asset belongs to exactly one Location at a time, so it has one clear home for access, work and reporting.
Equipment that travels (a portable pump, an inspection vehicle): give it the Location that is its home base, and give the teams that use it access to that Location.
The same kind of equipment in many places (a first-aid kit in every restroom): create a separate Asset at each Location. They're different physical items, each with its own history.
Equipment that permanently changes home: move it — see below.
Move an Asset to another Location
1. Select the Asset
Go to Locations › Assets (or a Location's Assets) and select the Asset.
2. Choose the new parent
Click Move. In Move asset to another location or asset, use the Location field to switch to the new Location, then select the Location or an Asset under it as the new parent.
3. Confirm
Click Confirm. Mobaro shows The asset was successfully moved.
A move takes the Asset's child Assets with it, and adds a Changed the location of the asset entry to each moved Asset's Show Activities history. Assignments on the moved Assets — open and closed — move to the new Location. Existing Results stay as they were. RideOps Assets can't be moved.
⚠️ Heads-up: Moving an Asset changes who can see it and its work. Members of the old Location who aren't members of the new one lose access, and the Asset's Assignments now appear under the new Location. Check the assignees on Schedules that target the Asset.
Check Asset Locations
Assets at Locations that are no longer in use — move them, or delete them if they're gone.
Assets created at the wrong Location — common during onboarding; they often surface when scheduled work reaches the wrong team.
Duplicates — the same physical Asset created twice. Keep one, move it to the right Location, and delete the other.
Troubleshooting
A User can't see an Asset. Search for it in Locations › Assets and check its Location column. Then check that the User is a member of that Location, directly or through a User Group or Location Group. To manage the Asset, their Role also needs Assets › Administrate.
Scheduled work for an Asset isn't reaching the right people. Assignees only get an Asset's Checklists if they have access to its Location. Use Schedule Metrics to check each assignee; see Asset-driven Assignments and Schedules.
Best practices
Give each physical item its own Asset record, so its history and work stay attached to that item.
Create Assets from the Location they belong to when you set up a new ride or area — it avoids picking the wrong Location.
Review Asset Locations at the start of each operating season.
Before moving an Asset, check who has access to the new Location.
Frequently asked questions
Can I move an asset to a different location?
Yes, in the Backend. Select the Asset, click Move, switch to the new Location and pick the new parent. You need Assets › Administrate at both Locations. The mobile app can't move Assets, and RideOps Assets can't be moved.
Can one asset belong to multiple locations?
No. An Asset belongs to exactly one Location. To let several teams work on it, give them access to that Location, or create separate Assets if they're separate physical items.
Users can't see the new assets I created. Why?
They need to be members of the Asset's Location — directly, through a User Group or through a Location Group — or be Super Users. Check the Location in Locations › Assets and the User's Location access.
Can I move many assets at once?
Not in one step. In the Backend, moving a parent Asset takes all its child Assets with it. For large moves, the Public API has a move endpoint, called once per Asset. See Bulk imports and API access for Assets.
Do assets have Location Properties?
No. Location Properties belong to Locations. When a Checklist runs against an Asset, logic based on Location Properties uses the Properties of the Asset's Location.
What happens to its assets if I delete a location?
Deleting a Location doesn't move or delete its Assets — they stay linked to the deleted Location. Move them to another Location first, so they stay visible and usable.