Bluebeam’s studio:// URI scheme (and equivalent web join links) currently opens/join a Session, but it doesn’t let us deep‑link directly to a specific document and page (or named destination) inside that Session. Enabling this would be a small change with big productivity and integration wins for teams and platforms that embed Bluebeam in their review workflows.
In coordinated, multi‑discipline reviews we often need to send someone straight to page X of document Y (e.g., “Spec Vol 2, p. 42, HVAC Notes” or “Sheet M1.02, Detail 7”). Today we have to provide written breadcrumbs like “Join Session ➝ open Volume 2 Specs ➝ go to p. 42 ➝ zoom to note.” That’s error‑prone, slow, and it disrupts reviewers who aren’t familiar with the document set.
Deep‑linking would reduce this to one click—reviewers land exactly where they need to comment, backcheck, or sign off.
Proposed enhancement:
Extend the Bluebeam protocol handler and web join URL to support document and location parameters. Examples below illustrate intent; actual names can follow Bluebeam conventions.
# Join a Session and open a specific document by GUID, at page 42 (fit width)
studio://studio.bluebeam.com/sessions/294-744-382?fileId=7f2a3...&page=42&zoom=fitWidth
# Named destination (preferred for resilient links across revisions)
studio://studio.bluebeam.com/sessions/294-744-382?fileId=7f2a3...&dest=HVAC_Notes_Section
# Snapshot view (x,y,zoom for precise detail callouts)
studio://studio.bluebeam.com/sessions/294-744-382?fileId=7f2a3...&view=150,230,200%
# Web equivalent (for Bluebeam on the web)
https://studio.bluebeam.com/join.html?ID=294-744-382&fileId=7f2a3...&page=42&zoom=fitWidth
Parameter ideas:
fileName or fileId document file name in the sessionpage: page numberdest or label: named destination or Place (Bluebeam can resolve to the correct page/zoom).view: snapshot coordinates/zoom (for details).zoom: inherit, fitWidth, fitPage, or numeric percentage.- Optional:
markupId for jumping to a specific markup in the record.
Thanks for considering!
James
