Overview
Library manuals support two advanced features that aren't obvious until you need them: Sections (named page ranges within a single PDF) and Versions (multiple variants of the same manual — typically for languages or role-based access). Together they let you maintain one canonical Library entry that serves many Checklist questions, many languages, and many audiences without duplicating content.
The mental model: A manual is the named entry in the Library (e.g., Coaster X Operator Manual). Each manual has one or more Versions (the actual PDF files — English, Spanish, etc.). Each Version can have Section mappings (named page ranges that let Checklists link to specific parts).
What Sections do
A Section is a named page range within a manual. Without Sections, every Checklist question linked to a manual loads the full PDF — every page, every time. With Sections, you can target the operator straight to the pages that matter.
Two reasons to use them:
Operator clarity — landing on page 47 of a 120-page manual is faster than scrolling.
Mobile data usage — Mobaro can fetch only the relevant pages instead of the whole document, which matters on cellular connections.
What Versions do
A Version is one of the actual PDF files attached to a manual entry. The most common reasons to have multiple Versions:
Language variants — one Version in English, one in Spanish, one in Danish. The User sees the Version that matches their preferences or Role.
Role-based access — a "technician" Version with full detail and an "operator" Version with just the operating procedure.
Manufacturer revisions — keep the previous Version available temporarily as the new one rolls out, in case operators need to reference the old document.
Note: Each Version has its own limited access setting. Use this to scope a Version to specific Roles or User Groups — useful for the technician/operator split or for restricting sensitive vendor documents.
The Section + Version workflow
The order of operations matters. Build Sections first conceptually (the names), then upload Versions, then map Sections to actual pages within each Version.
1. Define the Section names on the manual
When creating or editing a manual, add Sections by name — for example, Pre-opening checks, Lap-bar restraint, Brake system, Emergency procedures. These are the labels Checklists will reference.
2. Add a Version (upload the PDF)
Click + to add a Version. Give it a name (e.g., English v3.2), set limited access if needed, and upload the PDF.
3. Section mapping for the Version
After upload, you're prompted to map each Section name to the page range in this PDF. The English version might have Brake system on pages 42–58; the Spanish version of the same manual might have it on pages 38–55 due to translation differences. Each Version's mapping is independent.
4. Preview the section
Use Preview file in the mapping dialog to confirm the page range is correct before saving.
5. Repeat per Version
Each new Version gets its own page mapping. The Section names stay constant; the page numbers vary per Version.
Best practice: Section mappings are editable later via Edit Section Mappings — useful when a Version's PDF is updated and pages shift slightly. You don't have to redo Section definitions on the manual itself.
Worked examples
Example 1: Multilingual coaster manual
Scenario: A theme park has English-speaking and Spanish-speaking ride operators. The manufacturer ships one PDF per language. Both teams need to reference the same procedural sections.
Setup: One Library manual entry called Coaster X Operator Manual. Sections defined: Pre-opening, Daily checks, Restraint inspection, Emergency stop procedure. Two Versions uploaded: English v3.2 and Spanish v3.2. Section mappings done independently for each PDF (page numbers differ between the two languages). Limited access set so each operator's Role pulls the right Version automatically.
Result: Operators see the manual in their preferred language with no separate Library entries, no duplicated Checklist links, and no maintenance overhead when the manufacturer ships v3.3.
Example 2: Technician vs operator manual
Scenario: The manufacturer ships a 200-page service manual covering both daily operation and full mechanical maintenance. Operators only need pages 10–35 (operating procedures); technicians need the full document.
Setup: One manual called Coaster X — Service manual. Two Versions: Operator-facing extract (just pages 10–35 as a trimmed PDF, limited access to operator Role) and Full service manual (200-page PDF, limited access to maintenance Role). Sections mapped independently to each Version.
Result: Operators see only the relevant 25 pages; technicians see the full document. Both come from the same Library entry, so Checklist links don't have to know about the access split.
Example 3: Sections for fast jump-to-page navigation
Scenario: A 400-page water park ride manual has procedural details scattered across many chapters. Operators waste time scrolling.
Setup: Single English Version. Sections defined for every major procedure: Morning startup, Restraint check, Pump system, Slide surface inspection, Daily close, Emergency evacuation. Each Checklist question links to the precise Section it needs.
Result: An operator hitting "restraint check" question lands on pages 87–92 instantly instead of scrolling through 400 pages.
Anti-patterns to avoid
Watch out for these patterns, which defeat the whole point of the Library system:
Uploading a new file as a new manual instead of a new Version — every Checklist linked to the original keeps showing the old document. Use + Version on the existing manual when you have an updated PDF of the same document.
Skipping Section mapping on a new Version — if a Section isn't mapped, Checklist links targeting that Section break for this Version. Map every Section every time you add a Version.
Defining Sections that span the whole document — if a "Section" is pages 1–400, it's just the manual. Sections only earn their keep when they target a specific range an operator would otherwise have to find manually.
Creating a separate manual entry per language — duplicates content, fragments Checklist links, and means every update has to be applied to every entry. One manual, multiple Versions.
See also
Creating and managing your Library — for the basic Library setup, folder structure, and Checklist linking.
Frequently asked questions
Q: Can a Section span non-contiguous pages?
A: No. A Section is a single page range. If you need pages 10–15 and 50–55, define them as two Sections (e.g., Setup procedure and Shutdown procedure).
Q: What if Section names don't match between Versions?
A: Section names are defined at the manual level, not the Version level — so they're always the same set across Versions. What changes per Version is the page range each Section maps to.
Q: How does the system pick which Version a User sees?
A: Based on the limited-access setting on each Version. If a User has access to multiple Versions, they pick from a list.
Q: If I update a Version's PDF, do existing page-range Section mappings still work?
A: They reference the original page numbers. If the new PDF has pages shifted, you need to re-edit the Section Mappings via Edit Section Mappings on that Version.
Q: Can a Checklist question link to a specific Version, or just a Section?
A: Checklist questions link to the manual + an optional Section. The Version surfaces to the User based on their limited-access setting — the Checklist doesn't choose the Version.