Overview
Positions describe the places that Attendants staff around a ride, such as loading and unloading. Configure the Positions, eligible Attendants and required Competencies for each Location in RideOps Settings.
This article covers the Backend setup. For signing Attendants in and out on the tablet, see Signing in as an attendant. For the rest of RideOps Settings, see Setting up RideOps.
At a glance |
|
Who can do this | Super Users or a Role with Locations › Modify. To pick User Groups you aren't a member of, also User Groups › View. |
Where | Locations › a Location › RideOps Settings › Positions and Attendants |
Works on | Backend (web) to configure; RideOps on the tablet |
Availability | All organizations, on Locations with RideOps turned on |
Create a Position
1. Open RideOps Settings
In the Backend, go to Locations, open the Location and click RideOps Settings. RideOps must already be turned on for the Location; see Setting up RideOps.
2. Click Add Position
In the Positions panel, click Add Position. The Configure Position for location dialog opens.
3. Fill in the Position
Setting | What it does | Default |
Name | The Position name Operators see on the tablet. Required. | Empty |
Description | Optional. RideOps shows it behind an info icon next to the Position. | Empty |
Mandatory | The Position must have an Attendant before the Location can be opened. | Off |
Required Competencies | Attendants must hold an active Certification for all of them to staff this Position. | None |
If another Position on the Location already has the same name, Mobaro warns you and asks whether to create it anyway.
4. Save and repeat
Click Save, add any other Positions, then confirm the RideOps Settings dialog and save the Location. Drag Positions in the Positions panel to change the order they appear in on the tablet.
Choose who can attend
In the same dialog, the Attendants panel decides who can be signed in to this Location's Positions.
Attendants: add Users or User Groups. Attendants are a separate list from Operators; someone who should do both needs to be in both.
Required Competencies: only Attendants with an active Certification for all of these can attend any Position on this ride. They apply in addition to each Position's own Required Competencies.
🛑 Critical: When you add a User Group as Attendants, every member can attend this Location, without taking normal Location membership into account. Add individual Users if only some members should attend.
Edit or delete a Position
In the Positions panel, click the pencil icon to edit a Position, or the trash icon to delete it. To delete, type the Position's name to confirm. Changes take effect when you save the Location. A deleted Position no longer appears on the tablet, and past sign-ins to it stay in the Operational Log.
If you delete a Competency in Competencies, Mobaro also removes it from the Required Competencies of Operators, Attendants and every Position.
How Positions affect RideOps
Opening: while a Mandatory Position is empty, the ride's status card lists it under Positions that require an attendant and the ride can't be opened.
While open: if a Mandatory Position becomes empty, RideOps shows the ride as not ready and hides the dispatch and queue widgets until someone is signed in again.
Automatic sign-out: all Attendants are signed out when the Operator signs out or the ride is closed, and when a Downtime starts if your organization has turned on Sign out all attendants on downtime creation.
Record: each Attendant sign-in and sign-out is logged in the Location's Operational Log as Logged in as or Logged out as the Position.
For how this works on the tablet, see Signing in as an attendant.
Best practices
Tick Mandatory only for Positions the ride can't safely run without, so openings aren't blocked unnecessarily.
Tie Required Competencies to Certification Processes, so who can staff a Position follows training records.
Put Competencies every Attendant needs in the Attendants panel, and only Position-specific ones on each Position.
Use a short description to tell Attendants where to stand or what the Position covers.
Frequently asked questions
What is a position in RideOps?
A role around a ride that an Attendant staffs, such as Front Load or Unload. You create Positions per Location in RideOps Settings, and can make them Mandatory so the ride can't open until they're staffed.
How do I add staff members who will be signing in at rides?
Add them in the Location's RideOps Settings: under Operators for people who run the ride (they need a PIN Code), and under Attendants for people who staff Positions. See Setting up RideOps.
If a ride requires 2 competencies in RideOps, do they need both?
Yes. A person needs an active Certification for every listed Competency. For a Position, that means all of the Position's Required Competencies plus all of those in the Attendants panel.
Someone isn't showing up in RideOps for the location. Why?
Check they're in the right list: Attendants for Positions, Operators for running the ride, directly or through a User Group. If they appear greyed out, they're missing an active Certification for a Required Competency.
How do I link a competency to a RideOps tablet?
You don't link it to the tablet. Add it as a Required Competency for Operators, for Attendants or on a Position in the Location's RideOps Settings. Every tablet running that ride then enforces it.