Overview
Permission folders in the Mobaro Library allow you to control who can view or access files by assigning permissions to folders. You can specify both who should receive the files (publish recipients) and where the files apply (publish targets). This is particularly useful when distributing manuals, SOPs, safety procedures, or team-specific documents.
Create a permission folder
To create a permission folder:
Navigate to the Library
In the Mobaro Backend, go to Library in the left-hand menu.
Create a new folder
Click + Create Folder at the top of the left panel to create a new folder. Name the folder and optionally add a description.
Set folder permissions
Add individual users or user groups who should be able to view the contents in Publish Recipients. Add locations or location groups that these files should be associated with Publish Targets.
Tip: Permissions applied at a top-level folder will automatically apply to any subfolders underneath it.
How permissions work
Publish recipients determine who can view the files.
Publish targets determine which locations the files appear for.
Files in a folder will only be visible to users who are both:
Included as a recipient, and
A member of a location or location group in the publish target.
This ensures precise delivery of content without cluttering the view of users who don't need access.
Special use case: RideOps manuals
Manuals intended for RideOps operators must meet both of the following criteria to be visible in the RideOps tablet under the Manuals section:
A Publish Recipient must be assigned (typically a user group such as "Ride Operators").
A Publish Target must be selected that links the manual to a specific location (e.g. a ride).
If either is missing, the manual will not appear in RideOps for operators.
Reminder: The manual section in RideOps is populated dynamically based on these permissions.
Frequently asked questions
Q: What happens if I don't set any permissions on a folder?
A: No users will have access to the folder and its contents by default unless inherited permissions from a parent folder allow visibility.
Q: Can subfolders have different permissions than the parent?
A: Yes. Subfolders can add to inherited permissions if explicitly edited, but cannot remove inherited parent-level permissions.
Q: Can I hide folders from the backend Library for certain users?
A: Yes. Backend access to the library relies on a user inheriting the View: Manuals and Directories permission.
Q: Do I need to set both recipients and targets every time?
A: It depends. For backend access only, you can get by with just recipients. For RideOps, both are required.