Overview
The signed-in Operator manages Attendants on the RideOps tablet. The Operator assigns people to Positions, switches Attendants during the day and signs them out. Attendants do not use a PIN for this process.
For setting up Positions and Attendants in the Backend, see Getting started with attendants and positions.
At a glance |
|
Who can do this | The Operator signed in on the tablet, for Users listed as Attendants on the Location |
Where | RideOps › the Operator's name at the top › Positions, or the ride's status card |
Works on | RideOps |
Availability | All organizations, on Locations with Positions set up |
Who can be signed in
An Attendant can be signed in to a Position when they:
are listed under Attendants in the Location's RideOps Settings, directly or through a User Group;
hold an active Certification for every Required Competency in the Attendants panel; and
hold an active Certification for every Required Competency on that Position.
Anyone missing a Competency appears greyed out. Tapping them shows Missing Competencies with the Competencies they lack.
Sign in an Attendant
1. Sign in as the Operator
An Operator must be signed in first. See Operating a ride in RideOps.
2. Open the Positions list
Tap the Operator's name at the top of the screen (it shows & # attendant(s) when Attendants are signed in). The Operators page lists the ride's Positions. While the ride is not ready, empty Mandatory Positions are also listed on the status card under Positions that require an attendant.
3. Tap Sign in and choose the Attendant
Tap Sign in on an empty Position, then tap the Attendant. Use Search to find a name. The Position then shows the Attendant and how long they've been signed in.
Signing in needs a connection. If it fails, RideOps shows Attendant sign in failed; check the connection and try again.
Switch or sign out
A staffed Position has two buttons:
Switch: choose another Attendant, who takes over the Position straight away.
Sign out: removes the Attendant and leaves the Position empty.
🛑 Critical: Signing out of a Mandatory Position leaves the ride not ready for operation: RideOps hides the dispatch and queue widgets until the Position is staffed again. Use Switch on Mandatory Positions to avoid a gap.
Automatic sign-out
RideOps signs all Attendants out of the Location when:
the Operator signs out (handing over with Switch to another Operator keeps the Attendants signed in);
the ride is closed; or
a Downtime starts, if your organization has turned on Sign out all attendants on downtime creation in Configuration › RideOps.
Where sign-ins are recorded
Each sign-in and sign-out is recorded in the Location's Operational Log as Logged in as or Logged out as the Position, with the User and time. See Log book on the web — the Operational Log dialog.
Best practices
Staff Mandatory Positions before the Preopening Checklist is done, so they don't hold up opening.
Use Switch for breaks and rotations, so the log shows an unbroken record for the Position.
Re-staff Positions after a Downtime if your organization signs Attendants out on Downtime.
Frequently asked questions
When we try to add someone to a required position it says nobody has the competencies. Why?
The Attendant needs an active Certification, not just the Competency, for every Required Competency on the Position and in the Attendants panel. An expired Certification doesn't count. See Getting started with attendants and positions.
How do I sign out of a ride on the tablet?
That's the Operator: tap your name at the top, then Sign out, or Switch to hand over. Signing out signs all Attendants out too. See Operating a ride in RideOps.
Do attendants need a PIN or password to sign in to a position?
No. Attendants don't use a PIN or password in RideOps. The signed-in Operator signs them in and out. Only Operators need a PIN Code.
Can I see who was logged in with what position?
Yes. The Location's Operational Log shows each Attendant sign-in and sign-out as Logged in as or Logged out as the Position, with the User and time. See Log book on the web — the Operational Log dialog.