Overview
RideOps Keys in Mobaro are essential for enabling and managing RideOps functionality across specific locations. A RideOps Key defines the rides and locations accessible to Operators, ensuring streamlined and controlled operations.
Creating a New RideOps Key
RideOps Keys are created in the Configuration section of the Mobaro Backend.
To create a new RideOps Key:
Navigate to Configuration
In the Mobaro Backend, go to Configuration > RideOps.
Open the RideOps Keys Section
Click on the RideOps Keys section to view all existing keys.
Click + Create
Click the + Create Key button to open the configuration window.
Name the Key
Enter a descriptive name for the key (e.g., "Airplane Carousel Operations").
optional
Limit to Locations
Assign specific locations to the key by selecting them from the Limit to these locations field.
If no locations are assigned, the key will apply to all locations.
optional
Enable Switching Between Locations
Check the box for Allow Operators to switch between locations added onto this RideOps key if Operators need access to multiple rides under the same key.
Save the Key
Click Create to finalize the RideOps Key.
Tip: Use descriptive names for keys to ensure they are easily identifiable for Operators and administrators.
Managing Existing RideOps Keys
To edit or update an existing RideOps Key:
Navigate to Configuration
Go to Configuration > RideOps in the Mobaro Backend.
Locate the Key
Find the key you want to edit in the RideOps Keys section.
Edit Key Settings
Click the Edit icon next to the key to open its settings.
Modify the name, location restrictions, or permissions as needed.
Save Changes
Click Update to save your changes.
To delete a RideOps Key:
Follow steps 1–2 to locate the key.
Click the Trash icon next to the key.
Confirm the deletion in the pop-up dialog.
Warning: Deleting a key immediately revokes access for any Operators or locations tied to it. Ensure the key is no longer in use before deleting it.
Best Practices for Managing RideOps Keys
Limit Locations for Security: Assign keys only to the locations where they are needed to minimize access risks.
Enable Location Switching Only When Necessary: Allow Operators to switch between locations only when they need to manage multiple rides under the same key.
Audit Keys Regularly: Review and update keys periodically to ensure they align with operational needs.
Frequently Asked Questions
Q: Can I create multiple keys for the same location?
A: Yes, you can create multiple keys for a location if different groups of Operators need varying levels of access.
Q: What happens if a key is deleted?
A: Operators tied to the deleted key will lose access to the associated locations. Create a new key to restore access.
Q: How do I assign a RideOps Key to an Operator?
A: Operators are assigned access automatically based on the key's associated locations. No additional assignment is required.