Overview
A RideOps Key is the credential a tablet uses to log into the RideOps app. The Key defines which Locations a tablet can operate, so creating and scoping Keys correctly is how you control where RideOps can be used across the park.
Users must be Super Users or have a Role with permission to manage Configuration to create or manage RideOps Keys.
Why this matters: The Key is what ties a physical tablet to the rides it's allowed to run. Scope each Key to the Locations it actually needs and your access stays tidy and secure; create one sprawling Key for everything and any tablet can open any ride. Getting Keys right is the foundation of a controlled RideOps rollout.
Creating a RideOps Key
RideOps Keys are created in the Configuration section of the Mobaro Backend.
1. Open Configuration > RideOps
In the Mobaro Backend, go to Configuration > RideOps, then open the RideOps Keys section to view existing Keys.
2. Click + Create Key
Click + Create Key to open the configuration window, then give the Key a clear, descriptive name (for example, Coaster Plaza Tablets).
3. Scope the Key (optional)
Use the Limit to these locations field to assign specific Locations to the Key. If you leave it empty, the Key applies to all Locations. To let Operators move between rides on the same tablet, check Allow Operators to switch between locations added onto this RideOps key.
4. Save the Key
Click Create to finalize the Key.
Best practice: Use one Key per area of the park rather than one per ride. It cuts Key-management overhead while keeping access scoped sensibly, and descriptive names keep Keys easy to identify for Operators and administrators.
Managing existing Keys
1. Locate the Key
Go to Configuration > RideOps and find the Key in the RideOps Keys section.
2. Edit its settings
Click the Edit icon next to the Key to change its name, Location restrictions, or switching behaviour, then click Update to save.
3. Delete a Key
To remove a Key, click the Trash icon next to it and confirm in the dialog.
Critical: Deleting a Key immediately revokes access for any tablets and Locations tied to it. Make sure the Key is no longer in use before deleting it.
Frequently asked questions
Q: Can I create multiple Keys for the same Location?
A: Yes. Create multiple Keys for a Location if different groups of Operators or tablets need separate access.
Q: What happens if a Key is deleted?
A: Tablets tied to the deleted Key lose access to the associated Locations. Create a new Key to restore access.
Q: How do I assign a Key to an Operator?
A: You don't assign Keys to Operators directly. A Key scopes which Locations a tablet can operate; Operator access is then controlled by who is listed as an Operator on each Location and the Competencies they hold. See Setting up RideOps.
Q: Can one Key cover multiple Locations?
A: Yes. Add several Locations to a Key and enable switching so Operators can move between them on the same tablet.