Overview
Mobaro tracks structural changes to Assets as they happen — when they're created, edited, and moved through the hierarchy or between Locations. The Asset history view gives you a chronological record of who did what and when, so you can answer questions like "when did this Asset move under Electrical System?" without digging through emails or change requests.
Why this matters: Even small structural changes to your Asset library can have downstream effects on Schedules, Assignments, reporting filters, and the daily mental model your team relies on. Having a record of those changes — even a partial one — makes troubleshooting and onboarding faster, and makes sure no change is silent.
Required access: Viewing Asset history requires the same permission level as editing Assets — typically Locations: Modify. Read-only Roles may not have full access to the history view.
What's tracked today
Mobaro's Asset audit trail currently captures three event types:
Creations — when an Asset is created, the history records who created it, when, and the Location it was created under.
Edits — changes to the Asset's editable fields (name, description, manufacturer, model, etc.) are logged with the timestamp and the User who made the change.
Moves — reparenting an Asset (changing its parent in the hierarchy) or moving it between Locations is logged so the structural lineage is reconstructable.
What's not tracked today
Heads up: The Asset audit trail is intentionally focused on structural changes today. The following are not captured in the Asset's history view:
Schedule and Assignment associations — adding or removing an Asset as a Target on a Schedule is not part of the Asset history (those changes live with the Schedule itself).
Result and inspection events — Checklists completed against the Asset are not in the history view; use the Gallery or Reports for that.
Bulk operations via the API — the events are recorded the same way as UI edits, but with the API key's name attribution rather than the human operator behind the integration.
Deleted Asset history — once an Asset is deleted, its history is no longer surfaced through the standard view.
A note on what's coming
Mobaro is working toward a more comprehensive Asset audit log over time — with broader event coverage, field-level diffs where appropriate, and richer filtering. The current view is the foundation that will be expanded.
Note: If you have a specific audit requirement that isn't covered by what's tracked today — for compliance, regulatory, or internal governance reasons — share the requirement with your Customer Success Manager. Concrete needs help shape what gets built next.
Working around the gaps today
If you need a fuller record of what changed and when while the audit log is still expanding, several pragmatic patterns work well:
Periodic exports via the API
Pull the full Asset list from the API (GET /api/customers/assets) on a schedule — daily or weekly — and store snapshots in your data warehouse, Excel, or version control. See Getting started with the Mobaro API.
External change request log
For organizations that need formal change control, route Asset structural changes through a separate ticket or change-request system (Jira, ServiceNow, etc.). The ticket holds the "why" and the approver; the Mobaro history holds the "when" and the "who." Together they reconstruct the full picture.
Encode change context in names and descriptions
If a structural change matters operationally (e.g., an Asset replaced after a major component swap), encode that in the Asset's Description field with the date and reason. This won't show in the history view, but it makes the Asset itself self-documenting.
Best practice: For regulated environments (compliance audits, ride safety inspections, certifications), pair the in-app Asset history with periodic API snapshots. Two independent records protect against missing events in either system, and the snapshots double as a disaster-recovery backup of your Asset library structure.
Anti-patterns to avoid
Watch out for these habits that hide changes the system can't fully capture today:
Treating the history view as a complete audit record — it's a partial record today. For compliance use cases, supplement it with external snapshots or a change-request system.
Repurposing existing Assets instead of replacing them — if a physical component is swapped, edit-in-place loses the lineage. Where regulation requires it, retire the old Asset and create a new one rather than rewriting the existing record.
Bulk-renaming through the API without context — API edits show up with the API key's User attribution. If multiple people share an automation key, the history can't tell you who actually triggered the change.
See also
Creating an Asset — the create flow and required fields, which is what the first event in any Asset's history records.
Linking Assets to Locations — for how Asset-to-Location moves are recorded.
Asset hierarchies and parent/child relationships — for what hierarchy moves look like in the audit trail.
Getting started with the Mobaro API — for setting up periodic export workflows.
Frequently asked questions
Q: Where does the Asset history view live?
A: From an Asset's detail panel in the Mobaro Backend, look for the history or audit section. Open an Asset from the tree view on its Location's Assets tab, or from the flat Locations > Assets list.
Q: Can I see exactly which field changed in an edit event?
A: Yes, the current history records that an edit occurred, by whom, and when and includes the before/after values for each field.
Q: Are API changes attributed to a User?
A: Yes, but the attribution is the API key's name, not the human operator behind the integration. If multiple people share a key, the trail won't distinguish between them. For better attribution, scope keys narrowly per integration or per operator.
Q: Does the history capture changes to Schedules or Assignments that target this Asset?
A: No. Those events live on the Schedule or Assignment, not on the Asset. To trace Schedule changes, look at the Schedule's own configuration history where supported.
Q: If I delete an Asset, is its history preserved?
A: The history of a deleted Asset is no longer surfaced through the standard view once the Asset is removed. For long-term records, export Asset data via the API on a periodic basis.
Q: Will Mobaro add a more comprehensive audit log?
A: A fuller audit log is the direction Mobaro is heading. The current implementation is intentionally focused on creations, edits, and moves — the events most likely to surprise downstream Schedules and reports — with broader coverage planned over time. If you have specific audit requirements, share them with your CSM.