Overview
Assignments are how Mobaro tracks work that needs doing — a failed inspection item, a repair, a safety follow-up or planned maintenance. Each Assignment belongs to a Location, has one or more assignees, and moves from Created to Started to Finished.
This article explains what an Assignment is made of, where Assignments come from, and how standard Assignments differ from those that use an Assignment Definition. For the steps, see How to create and delegate an assignment.
At a glance |
|
Who can do this | Any User in your organization can create Assignments. An Assignment Definition's Who can create can limit who creates that type |
Where | Assignments in the Backend; Assignments in the mobile app |
Works on | Backend (web), Mobile app, Public API |
Availability | All organizations. Assignment Definitions are an add-on (see below) |
💡 Why this matters: Assignments turn issues into owned, documented, trackable work. Understanding the model — status, priority, category, Location and origin — is what lets you report accurately and keep Locations and Assets ready for operation.
What an Assignment is made of
Every Assignment has the same core fields, whether it's a standard Assignment or uses an Assignment Definition.
Field | What it is |
Title | A short name for the task, such as Replace loose handrail. Required. |
Location and Asset | The one Location where the work happens (required), optionally narrowed to an Asset at that Location. |
Assigned to | The Users and User Groups who do the work. |
Status or State | Created, Started or Finished; a definition's own states otherwise. |
High priority or Priority | A checkbox on standard Assignments; the definition's priorities otherwise. |
Assignment Categories | Labels for filtering and reporting, such as Maintenance. |
Starts at / Ends at | When work can start, and the deadline that drives overdue tracking. |
Description, comments and attachments | Context, progress notes and photos. The resolution is recorded when the Assignment is finished. |
Subscribers | Users who follow the Assignment and get notifications about it without being assigned. |
The activity feed records every status change, comment and reassignment, so each Assignment carries its own audit trail. For what each status means and who can change it, see Understanding assignment statuses.
Where Assignments come from
Manually — from Assignments in the Backend, or in the mobile app.
From a Checklist — raised on a question that has Allow assignments turned on, or automatically by an Assignment trigger when an answer meets a condition. The Assignment is linked to the Result.
From a Downtime or a Note — when your organization has set this up. The Assignments table shows these as From Downtime or From Note.
Through the Public API — from another system.
Assignments are one-off tasks: there are no repeating Assignments. For recurring work, schedule a Checklist and let its triggers raise Assignments when needed.
Standard Assignments and Assignment Definitions
Out of the box, every Assignment uses the standard statuses, the High priority checkbox and your organization's Assignment Categories. An Assignment Definition replaces these with a workflow you design for one type of work, such as a work order or a parts request.
Setting | Standard Assignment | With an Assignment Definition |
States | Created, Started, Finished | Your own Initial, Step and Final states |
Priority | High priority checkbox | Your own priorities, optionally Critical for operation |
Categories | Organization Assignment Categories | The definition's own categories, organization categories, or both |
Who can create | Any User in the organization | Can be limited with Who can create |
Who can be assigned | Users with access to the Location, and User Groups with Assignments ticked under Assignability that have at least one such member | Can be limited with Who can be assigned and Limit type of assignee to |
Assignment Definitions are an add-on that Mobaro enables for your organization (Assignment Definition functionality). Ask your CSM.
Where Assignments show up
Assignments in the Backend — the working list, with filters for status, priority, Location, Asset and assignee. The Open filter shows everything that isn't Finished.
Mobile app — assignees see and work on their Assignments in the field.
Dashboards — widgets such as the Assignment Overview widget summarize Assignments by category, assignee, Location and status.
Location readiness — open Assignments can turn a Location red on the Location Overview (see below).
🛑 Critical: With Red if one or more active high priority assignments exist turned on — it is by default — any open High priority Assignment, or one at a Critical for operation priority, turns its Location red (not ready) until it's finished. Red if one or more active overdue assignments exist does the same for overdue Assignments. See Schedule criticality and Location operational status.
Example: a failed handrail check
During a daily coaster inspection, a ride operator answers Not OK to the handrail question. That answer has an Assignment trigger that assigns the Maintenance User Group and sets the category to Maintenance.
The app shows the operator a prefilled Assignment to confirm, unless the trigger is set to create it without user intervention. The Assignment is created at the ride's Location, linked to the Result, and appears in the Maintenance team's list in the app and on the Assignment Overview widget.
Best practices
Start with standard Assignments. Add an Assignment Definition only when a team needs more states, its own priorities, or limits on who can create, be assigned or resolve.
Assign to User Groups rather than individuals, so work still gets picked up when someone is off shift.
Use High priority only for work that should stop operation — with the default Location Overview settings, it turns the Location red.
Frequently asked questions
What is an assignment definition, and do I need one?
An Assignment Definition is a custom workflow for one type of Assignment, with its own states, priorities, categories and access rules. You don't need one — standard Assignments work for everyone. Definitions are an add-on; see Using Assignment Definitions.
Can I move existing assignments onto an assignment definition?
Yes. In Assignments, select them — they must all have the same definition — and use Change Assignment Definition to map their statuses to the new definition's states. See Change an assignment's assignment definition.
Do users need a role permission to create assignments?
No. Any User in your organization can create Assignments; Roles only control viewing, modifying and deleting others' Assignments. An Assignment Definition can limit who creates its type. See How to create and delegate an assignment.
Will finishing the assignment make the ride ready again?
Yes, if that Assignment was what turned the Location red. Once it's Finished, the Location turns green unless something else still holds it red, such as a missing critical Checklist.