Internal project workspaces are built for organization and editing. Clients, owners and outside stakeholders usually need something simpler: a clear view of the documentation they were meant to receive.
What a Published Viewer is
An OcuMap Published Viewer is a curated, read-only project experience created from existing project content. It is designed for browser-based delivery without giving the recipient access to the internal workspace.
Why separate delivery from production
- Keep internal organization and administration private
- Share only the content relevant to the recipient
- Reduce the need to package large folders for every handoff
- Present maps, floor plans and visual records in spatial context
- Give stakeholders a repeatable link instead of a one-time download
Controls for external access
Published Viewers can be configured with project-level sharing controls such as password protection, download settings and expiration where enabled. Comments and guest participation can be managed according to the publishing configuration.
Use the same documentation, not a duplicate project
The Published Viewer references project content that already exists in OcuMap. That reduces the need to maintain a separate delivery copy every time the project changes.
Common uses
- Owner handover
- Existing-condition documentation delivery
- Inspection and assessment packages
- Construction progress records
- Facility and capital-planning references
- Client review of infrastructure or site documentation
Preserve the long-term record
Published delivery is only one part of the workflow. Original files and internal project context remain preserved in the organization so the same documentation can support future work.
Create your first OcuMap project →
Practical checklist
- Decide who needs workspace access and who only needs a published view.
- Curate the smallest useful set of documentation for each audience.
- Configure sharing controls before sending the link.
- Verify download and comment settings.
- Test the viewer on desktop and mobile.
- Keep internal records and original files in the organization workspace.
Related resources
Common questions
Does the recipient need an OcuMap account?
Published Viewers are designed so stakeholders can review shared documentation without being added to the internal project workspace.
Can the publisher control access?
Yes. Viewer settings can include controls such as passwords, download permissions and expiration where configured.
Does publishing duplicate the project?
No. The Published Viewer references selected project content rather than requiring a separate manually maintained copy.