Solutions · By document

Manuals

The document that must always be current

A manual starts aging the moment it circulates as a file. Support tickets arrive quoting yesterday's copy, and after a re-send you still can't tell which edition is out there. Distribute one link and swapping the file never changes the address — every copy of the link that's already out there points at the latest edition automatically.

Same-link versioningURLs stay putQR inside the PDFData room bundles

Recommended settings

What we'd recommend for a manual. Set these on the link as you create it.

  • Same-link versioning ON
  • Existing URLs kept ON
  • Viewer shortcut QR ON
  • PDF download ON
  • Data room bundle ON
  • Email open alerts OFF
Create a link with these settings

After sending, you see this

Once you can see where users get stuck, the manual's structure changes.

  • Cover 0:08
  • Setup 1:47
  • Basics 2:33
  • Troubleshooting 2:02
  • FAQ 1:11
  • Contact 0:24

Real-time open alert

Swapped in manual v3.2 · same link

Links already distributed show the latest version from their next view

INSIGHT

Stay time on Troubleshooting keeps growing. Folding that content into Basics would cut the repeat tickets.

Workflow

Manuals, step by step

Upload, set, send, check. No rebuilding files, and nothing for the reader to install.

  1. 01 Upload the manual

    Upload the latest PDF and create one distribution link.

  2. 02 Standardize on that one link

    Product pages, customer emails, printed QR codes, the internal wiki — the same address everywhere.

  3. 03 On a revision, swap only the file

    Upload the new PDF and it goes Live; the distributed address doesn't change.

  4. 04 Find where users get stuck

    Pages that pool stay time are where users wander. Move those items forward in the next revision.

Key features

Manuals: the features at work

The features actually used when sending this document. Each links into the features page, and what each plan includes is on the pricing page.

Same-link versioning

Upload a new PDF and it becomes the Live version behind the same address. Rolling back to a previous version is instant, and reading data can be viewed per version. A version upload uses one monthly upload.

URLs stay put

The addresses already sitting in product pages, customer emails, and the internal wiki never need to change. The more distribution paths you have, the more managing one link pays off.

QR in the printout

Turn on 'Add viewer shortcut QR code' in the link settings and downloaded PDFs carry a QR code. Print and distribute — scanning always opens the current web viewer. This option is for links with PDF download allowed.

Manual bundle pages

Bundle the install guide, operations manual, and release-note links into one data room served as a public page. Groups nest up to 5 levels, so even a large product family stays organized.

Find the sticking points

Per-page stay time and return-visit share reveal which item users wander on. Fix the document before the tickets pile up.

Page jumps · demo videos

Lay page-jump areas over a long manual for per-item navigation, and put demo videos right on the tricky steps. Page jumps work in downloaded PDFs too.

FAQ

Manuals — check before you send

Does swapping the file change the link address?

No. Upload the updated PDF and the existing share address stays exactly the same, showing the latest content from the next view.

Can I roll back a bad upload?

Restore a previous version from the version list and it takes effect immediately. The restored version inherits the public/private state of the version it replaces.

Do printed manuals also lead to the latest edition?

The QR points at the link, not the file, so scanning opens whatever is the latest web viewer at that moment. The printed QR image itself stays fixed to the link and page info from print time.

Related guides

Want the setup steps?

The product guides walk through each step with real screens.

Put your manual behind one link

Start free and see the flow where a file swap keeps everything current.