A public page is the simplest way to share client work without requiring sign-in. It is also the widest access level in Link, so always preview the page and review its contents before making it public.
What public means
Anyone who has the page’s Link can open a public page. They do not need an account, an invitation, or an email address approved for your workspace.
Preview before publishing
Link admins and client admins can preview a private page as a public visitor before changing its visibility.
- Open the client, project, or nested page while signed in.
- Open the page menu and choose View as.
- Select Visitor using.link/[code].
- Review the page from top to bottom while the public-preview warning is visible.
- Select You to return to your own permissions, or use the X to close View as.
Automatic redaction
When automatic redaction is enabled for your workspace, Link removes configured sensitive text before public pages and Visitor previews are sent to the browser. The source page in Notion and private signed-in views are not changed.
Redaction checks page text, titles, breadcrumbs, tables, code, captions, filenames, link labels, URLs, menus, and page metadata. Location protection is deliberately label-aware: it does not guess arbitrary place names in prose. Redaction does not read text inside images, PDFs, video, audio, external documents, linked pages, or any other file contents. Open and review every attachment separately.
Check sensitive information
Read the page as if the link had been forwarded outside the client team. Remove anything that should not be available without sign-in.
- Review every visible redaction label, or confirm that hidden-style omissions leave the page complete and natural.
- Open every image, file, and nested page that remains visible in the preview.
- Check headings and summaries for internal language or unapproved claims.
- Confirm that private sibling projects and pages do not appear in navigation.
- When in doubt, keep the page private and invite the intended people instead.
Make the page public
Exit View as, open the page’s access controls, and change the visibility from Private to Public. Copy the exact page link and open it in a signed-out browser before sending it.
Publishing a project does not automatically publish every nested page. Review each nested page separately when it contains material that should be shared.
Make the page private again
Change the visibility back to Private whenever broad link access is no longer appropriate. People will then need the correct signed-in workspace or client access to open it.
Making a page private blocks the public link, but it cannot undo information that someone already viewed, copied, or downloaded while the page was public.