Overview
Permission folders in the Library control who can see content and where it applies. Each Folder carries two settings — Publish Recipients (who can view) and Publish Targets (which Locations the content belongs to) — so you can distribute manuals, SOPs, and safety procedures precisely to the teams and rides that need them.
Users must be Super Users or have the following Role to create and manage Library folders:
Library: Create
Why this matters: Without scoping, every User sees every document. Publish Recipients and Targets keep each team's Library focused on what's relevant to them — and they're what makes manuals appear in the right ride's RideOps tablet.
How folder permissions work
Two settings decide visibility, and a Folder's content appears only to Users who satisfy both:
Publish Recipients — the Users or User Groups who can view the content.
Publish Targets — the Locations or Location Groups the content is associated with.
A User sees a Folder's files only when they are a recipient and a member of a Location (or Location Group) in the Publish Target. This delivers content precisely without cluttering the view of Users who don't need it.
Note: Permissions inherit downward — settings on a top-level Folder automatically apply to its Sub-folders. A Sub-folder can add recipients or targets, but it can't remove what it inherits from the parent.
Creating a permission folder
1. Open the Library
In the Mobaro Backend, go to Library in the left-hand menu.
2. Create a new Folder
Click + Create Folder at the top of the left panel. Give the Folder a name and an optional description.
3. Set Folder permissions
Add the Users or User Groups who should see the content under Publish Recipients, and add the Locations or Location Groups the content belongs to under Publish Targets.
Best practice: Set permissions on the highest Folder that should share them and let Sub-folders inherit. It's less to maintain and avoids gaps where a Sub-folder is missing a recipient or target.
Special case: RideOps manuals
For a manual to appear in the Manuals section of the RideOps tablet, its Folder must have both:
A Publish Recipient — typically a User Group such as Ride Operators.
A Publish Target that links the manual to a specific Location (the ride).
Heads-up: The RideOps Manuals section is populated dynamically from these permissions. If either the recipient or the target is missing, the manual won't appear for operators.
Example: ride manuals for one team
Scenario
The maintenance crew needs the manufacturer manuals for the park's coasters — visible to them in the Backend and in RideOps on those rides, but not cluttering everyone else's Library.
Setup
An administrator creates a Coaster manuals Folder and uploads each ride's manual.
Publish Recipients is set to the Maintenance Team User Group; Publish Targets is set to the coaster Locations.
Result
The crew sees the manuals in the Library and in the RideOps Manuals section on those coasters. Users outside the team — or at other Locations — don't see the Folder at all.
Frequently asked questions
Q: What happens if I don't set any permissions on a Folder?
A: No Users have access to the Folder or its contents unless permissions are inherited from a parent Folder.
Q: Can Sub-folders have different permissions than the parent?
A: A Sub-folder can add to inherited permissions, but it can't remove the recipients or targets it inherits from the parent.
Q: Can I hide Folders from the Backend Library for certain Users?
A: Yes. Backend access to the Library depends on the View: Manuals and Directories permission in a User's Role.
Q: Do I need to set both recipients and targets every time?
A: It depends. For Backend access alone, recipients can be enough. For content to appear in RideOps, both recipients and a Location target are required.