Barcode sign-in speeds up the Operator sign-in step in the RideOps app. Instead of scrolling or typing to find their name in the Operator list, an Operator scans their badge and RideOps jumps straight to them — matching the badge to their External ID. They still enter their PIN to sign in; the badge only selects the right Operator.
Why this matters: On a shared tablet with a long Operator list, finding yourself by scrolling or typing takes time at a busy sign-in moment. Scanning a badge selects the right Operator instantly, while the PIN still does the actual authentication — so you get the speed without loosening security.
What's covered:
Before you start
To turn barcode sign-in on, you must be a Super User or have a Role with permission to manage Configuration. For it to work for a given Operator, that Operator's User record needs an External ID that matches the value encoded on their badge.
Barcode sign-in is an organization-wide setting — enabling it applies across your RideOps Locations, rather than being configured per ride.
Enable barcode sign-in
1. Open Configuration > RideOps
In the Mobaro Backend, go to Configuration and select the RideOps tab.
2. Find the RideOps settings panel
Locate the RideOps settings panel. It holds the organization-wide RideOps toggles, including Enable barcode sign-in.
3. Check Enable barcode sign-in
Tick Enable barcode sign-in. As the setting notes, this lets Operators sign in on the RideOps app by scanning a badge that matches their External ID.
Note: The same panel contains other organization-wide RideOps toggles, such as Sign out all attendants on downtime creation. Only change the settings you intend to.
Set an Operator's External ID
Barcode sign-in works by matching the scanned badge to an Operator's External ID, so each Operator who signs in this way needs that field set on their User record.
1. Open the User
In the Mobaro Backend, go to Users and open the Operator's profile.
2. Enter the External ID
Set the External ID to the value encoded on that Operator's badge, then save. For the full User setup, see Create new users in your organization.
Best practice: Keep External ID values consistent with the identifiers your badges already use — for example the staff number your access-control or HR system prints on the badge — so a single badge works across systems.
How Operators sign in with a badge
Once barcode sign-in is enabled and an Operator has a matching External ID, they scan their badge at the RideOps sign-in step. RideOps matches the badge to their External ID, selects them from the Operator list, and prompts for their PIN. They enter their PIN to finish signing in, exactly as they would after selecting their name manually.
Note: The badge doesn't replace the PIN — it only selects the right Operator so nobody has to scroll or type to find their name. Every Operator still enters their PIN to sign in. An Operator without their badge can select their name manually, as before, then enter their PIN.
Frequently asked questions
Q: Is barcode sign-in set per ride or for the whole organization?
A: It's organization-wide. You enable it once in Configuration > RideOps > RideOps settings, and it applies across your RideOps Locations.
Q: Does the badge replace the PIN?
A: No. The badge only selects the right Operator at sign-in — it saves scrolling or typing to find your name. You still enter your PIN to sign in, so the PIN remains the thing that authenticates you.
Q: What if an Operator doesn't have their badge?
A: They select their name from the Operator list manually, as before, then enter their PIN. Barcode sign-in is a shortcut for finding yourself, not a requirement.
Q: An Operator scans their badge but nothing happens.
A: Confirm barcode sign-in is enabled, and that the Operator's External ID exactly matches the value on their badge. A mismatch — or a missing External ID — means RideOps can't match the scan to a User, and they'll need to select their name manually.
Q: Does barcode sign-in change Competency or Operator requirements?
A: No. It only changes how an Operator finds themselves at sign-in. They still need to be listed as an Operator on the Location and hold any required Competencies. See Utilizing Competencies.
Q: Does this apply to Attendants too?
A: The setting covers Operator sign-in on the RideOps app. For how Attendants sign in to Positions, see Signing in as an attendant.