Publish a document to the web
Turn any project document into a public page — with optional guest comments, a password, and your own custom domain.
Some documents are for the team, and some are for the client: a scope, a launch checklist, release notes, a handover. Publish to web turns any project document into a page you can send, without exporting it to a PDF that is stale the moment it lands.
Publish
Open the document and use Share in the editor header, then switch Publish to web on. Pogpin creates a public link of the form /p/<slug>, and the control turns into a Live badge.
Two more switches sit under it:
- Allow public comments — readers can leave feedback on the published page. Off by default.
- Password protect — readers must enter a password before they see anything. Minimum four characters; you can change or remove it later without unpublishing.
Copy public link and Open public page do what they say. Turning the toggle back off unpublishes the document immediately — the link stops resolving.
Serve it from your own domain
By default a published document lives on a Pogpin URL. To serve it from your own, open Project settings → Custom domains — serve published documents from your own domain.
The flow is two DNS records:
- Add the domain. Pogpin shows a TXT record to prove you own it.
- Add that record at your DNS provider and press Verify. Until propagation catches up you will see DNS record not found yet — check again after propagation.
- Once the status flips from Pending verification to Verified, point the domain at Pogpin with the CNAME the panel shows.
White-label published pages and custom domains are part of the Pro plan and above — see pricing.
What to publish
Published documents work best as the thing you would otherwise paste into an email:
- a scope or estimate the client can comment on inline, rather than in a reply chain
- a release note that links back to the pins it closed
- a handover for whoever takes the project next
Because the page is generated from the live document, editing the document updates the page — there is no second copy to keep in sync.
Next
- Keep feedback on the published page moving: triage pins into tracked issues.
- Bring the right people in with the right access: invite your team and set roles.