Overview
Folders in the Library have two publishing settings — Publish Recipients (who receives the content) and Publish Targets (which Locations it's limited to). Together they decide which manuals, videos, and links reach each User in the mobile app and on RideOps, so you can deliver SOPs and safety procedures to the teams and rides that need them.
Publishing doesn't control the Backend. Who can open the Library in the Backend is set by Roles. To upload content, see Creating and managing your Library.
At a glance |
|
Who can do this | Super Users, or a Role with Manuals and Directories › Create (or Modify, to edit an existing folder). Users who created a folder can also change or delete it and the folders inside it. |
Where | Library › Create Folder, or select a folder › Edit |
Works on | Backend (web) to set up. Content is delivered to the mobile app and RideOps. |
Availability | All organizations |
💡 Why this matters: Without publishing settings, staff either miss the documents they need or wade through everyone else's. Recipients and Targets keep each team's Library focused — and they're what makes the right manuals appear on the right ride's RideOps device.
How folder publishing works
Publish Recipients — the Users or User Groups who receive the folder's content. Recipients are inherited by every folder below this one.
Publish Targets — Locations or Location Groups. Targets limit the files directly in this folder to Users who are members of those Locations. They aren't inherited by sub-folders.
In the mobile app, a User receives a folder's files when they're a Publish Recipient of that folder or of any folder above it, and — if the folder has Publish Targets — they're a member of one of those Locations or Location Groups. A folder with recipients but no targets reaches its recipients everywhere. See Finding and using Library content in the mobile app.
ℹ️ Note: Two things deliver content regardless of these settings. Super Users and Users whose Role has Manuals and Directories › View receive the whole Library in the app. And any manual, video, or link attached to a question on a Checklist a User has is always delivered to them.
In the Backend, the Library is shown to Super Users and to Users whose Role has any Manuals and Directories permission. People who build Checklists (Checklists › Create or Modify) can also browse it to attach content to questions. Publish Recipients and Targets don't change what anyone sees in the Backend.
Set up a folder
1. Open the Library
In the Backend, go to Library in the left-hand menu.
2. Create the folder
Select where the folder should go and click Create Folder. In Create new directory, enter a Name.
3. Set recipients and targets
Add the Users or User Groups who should receive the content under Publish Recipients. To limit the folder's own files to certain Locations, add Locations or Location Groups under Publish Targets. Click Save. To change the settings later, select the folder and click Edit.
RideOps manuals
The Resources & Manuals page on a RideOps device lists files from folders where the logged-in User is a Publish Recipient (directly or through a parent folder), and where the folder either has no Publish Targets or targets that ride's Location or one of its Location Groups.
⚠️ Heads-up: On RideOps, Manuals and Directories › View doesn't open the whole Library — only publishing counts. If a folder has recipients but no targets, its manuals appear on every ride the recipient operates. Add the ride as a Publish Target to keep a manual to that ride.
Example: ride manuals for one team
The maintenance crew needs the manufacturer manuals for the park's coasters, in the app and on RideOps at those rides, without cluttering everyone else's Library.
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.
The crew gets the manuals in the app and on the RideOps Resources & Manuals page on those coasters. Other Users don't receive them, unless they're Super Users, their Role has Manuals and Directories › View, or a manual is attached to one of their Checklists.
Delete a folder
🛑 Critical: Deleting a Library folder also deletes all of its sub-folders and every manual, video, and link in them. This can't be undone, and Checklist questions that used those manuals lose them. Move anything you want to keep before you delete.
Best practices
Set Publish Recipients on the highest folder that should share them, and let sub-folders inherit.
Put restricted content in a folder whose parent folders don't have broader recipients — a sub-folder can't remove recipients it inherits.
Use Publish Targets for ride-specific manuals, so RideOps shows each manual only at its ride.
Keep Manuals and Directories › View for people who manage the Library; for everyone else, rely on publishing.
Frequently asked questions
A user can't see a document in the Library on their phone. Why?
Check that they're a Publish Recipient of the folder, or of a folder above it, and — if the folder has Publish Targets — a member of one of those Locations. In the Backend, the Library also needs a Manuals and Directories permission in their Role.
I limited a sub-folder to two User Groups, but other users can still see it. Why?
Recipients on parent folders are inherited, so anyone on a folder above also receives it. Super Users and Users with Manuals and Directories › View receive the whole Library, and files attached to a User's Checklists are always delivered.
I removed a user group, but the files still show on RideOps. Why?
The group is probably still a Publish Recipient of a parent folder, which the sub-folder inherits. Check the folders above. If the folder has no Publish Targets, its files show on every ride its recipients operate.
What happens if I don't set any permissions on a folder?
If no folder above it has Publish Recipients either, its files aren't published to anyone in the app. Only Super Users and Users with Manuals and Directories › View receive them, plus anyone whose Checklist has one of the files attached to a question.