Overview
A RideOps Key connects a RideOps tablet to your organization. The key decides which Locations the tablet can run and whether Operators can switch between them. You enter or scan the key when you set up the RideOps app on a tablet (see Setting up the RideOps app as a PWA on tablets). Some teams call it the operations key. You don't assign keys to Operators: who can operate each Location is set in its RideOps Settings (see Setting up RideOps).
At a glance |
|
Who can do this | Create, edit and delete: Super Users only. See and show existing keys: Super Users or a Role with Organization › Administrate. |
Where | Configuration › RideOps › RideOps Keys |
Works on | Backend (web) to manage keys; RideOps on the tablet |
Availability | All organizations |
💡 Why this matters: The key is what ties a physical tablet to the rides it's allowed to run. Limit each key to the Locations it needs and access stays tidy and secure; one key for everything lets any tablet open any ride.
Create a RideOps Key
1. Open the RideOps tab
In the Mobaro Backend, go to Configuration and open the RideOps tab. Existing keys are listed in the RideOps Keys table.
2. Click Create
Click the + button (Create). In Create RideOps Key, enter a Name that says where the key is used, for example Coaster Plaza Tablets.
3. Choose Locations and switching
In Limit to these locations (Leave blank for all locations), pick the Locations tablets using this key may run. If you leave it blank, the key covers every Location with RideOps turned on. Tick Allow Operators to switch location if Operators should move between the key's Locations on the same tablet.
⚠️ Heads-up: If you pick Locations where RideOps isn't configured, the dialog warns you. Those Locations don't appear on the tablet until you turn on RideOps and fill in the Location's RideOps Settings. See Setting up RideOps.
4. Click Create
Click Create. Mobaro shows the key with a QR code: enter the key or scan the code on the tablet.
ℹ️ Note: Mobaro generates the 15-character key. You can't change or regenerate it; you can only edit the key's name, Locations and switching. To replace a key, create a new one, set up the tablets with it, then delete the old one.
Show an existing key
In the RideOps Keys table, keys are hidden as dots. Click the eye icon (Show) in the Key column to see the key and its QR code again. The Limited to locations column shows how many Locations a key covers, or None if it covers all of them.
Edit a key
Select the key's row and click the pencil button (Update). In Edit RideOps Key, change the name, Locations or Allow Operators to switch location, then click Update.
Delete a key
Select the key and click the trash can (Delete), then confirm with Delete in the Delete RideOps Key(s) dialog.
🛑 Critical: Deleting a RideOps Key cannot be undone, and every tablet using it loses access to RideOps. Set those tablets up with another key before you delete it.
Best practices
Use one key per area of the park rather than one per ride, and give each key a descriptive name.
Limit every key to the Locations its tablets need, and tick Allow Operators to switch location only where Operators really move between rides.
Remember that anyone with Organization › Administrate can show keys; share them only with the people who set up tablets.
Replace a key by creating the new one first, so tablets are never left without access.
Frequently asked questions
Where do I find our RideOps key (operations key)?
In the Backend under Configuration › RideOps, in the RideOps Keys table. Click the eye icon in the Key column to show the key and its QR code. You need to be a Super User or have Organization › Administrate.
How do operators switch between rides on the same tablet?
Add those Locations to the tablet's key (or leave the key unlimited) and tick Allow Operators to switch location on the key. Operators can then move between those Locations on the tablet.
I added a location to the key, but it doesn't show in RideOps. Why?
The Location must have RideOps turned on and its RideOps Settings filled in; otherwise tablets don't list it. Also check that the key's Limit to these locations includes it. See Setting up RideOps.
What permissions do I need to create a RideOps key?
You need to be a Super User. A Role with Organization › Administrate lets someone see and show keys, but not create, edit or delete them.