Publish Pages

Publishing a page generates a unique public URL that anyone can access without logging in to SetGet. Published pages are read-only for external viewers and display the page content in a clean, distraction-free layout. Use publishing to share documentation with clients, stakeholders, or the public.

How to publish a page

1. Open the page you want to publish.
2. Click the ... menu in the page header.
3. Select Publish.
4. A dialog appears with the generated public URL.
5. Copy the URL and share it with your audience.

The page is now publicly accessible. Anyone with the link can view it.

Publishing indicator

Published pages display a Published badge next to the page title. In the page list, a globe icon indicates that a page has been published.

Published page appearance

When an external viewer opens a published page, they see:

Element	Displayed
Page title	Yes
Page content	Yes, fully rendered with all formatting
Images and embeds	Yes
Tables	Yes
Code blocks	Yes, with syntax highlighting
Diagrams	Yes
Inline comments	No — comments are hidden from public view
Version history	No — only the current version is shown
Page properties	No — labels, access level, and metadata are hidden
Edit controls	No — the page is read-only
SetGet navigation	Minimal — a simple header with the workspace name

The published view is clean and optimized for reading. It uses the same typography and formatting as the editor but without editing controls or workspace navigation.

Managing published pages

Update published content

Published pages reflect the latest saved version. When you edit a published page in SetGet, the changes appear on the public URL after the next auto-save. There is no separate "deploy" step.

Disable publishing

To unpublish a page and revoke public access:

1. Open the published page.
2. Click the ... menu in the page header.
3. Select Unpublish.
4. Confirm the action.

The public URL immediately stops working. Anyone who visits the link sees a "Page not found" message.

WARNING

Unpublishing a page invalidates the URL permanently. If you publish the page again later, a new URL may be generated. Do not rely on the old URL continuing to work after unpublishing.

Regenerate link

If you need a fresh URL (for example, to revoke access for people who have the old link):

1. Unpublish the page.
2. Publish it again.
3. A new unique URL is generated.

Share the new URL with your intended audience. The old URL no longer works.

Who can publish

Role	Can publish	Can unpublish
Page creator	Yes	Yes
Project admin	Yes	Yes
Project member	No	No
Workspace admin	Yes	Yes

Publishing and access control

Publishing is independent of the page's internal access level:

Page access	Can be published	Public link behavior
Public (all project members)	Yes	External viewers see content; internal members edit normally
Private (creator only)	Yes	External viewers see content; only creator can edit
Locked	Yes	External viewers see content; nobody can edit

TIP

You can publish a private page. This is useful when you want external stakeholders to view a document that only you can edit. The page remains invisible to other project members while being publicly accessible via the link.

Use cases

External documentation

Publish API documentation, integration guides, or product manuals that clients or partners need to reference. Update the page in SetGet, and the public link always shows the latest version.

Stakeholder updates

Share project status updates, quarterly reviews, or milestone summaries with executives or external stakeholders who do not have SetGet accounts.

Public knowledge base

Publish a collection of pages as a lightweight public documentation site. Each page gets its own URL that you can link from your website or support portal.

Interview and onboarding material

Publish pre-read material for candidates or new hires before they have access to your workspace.

Request for comments

Publish a draft proposal or RFC and share the link for external review. Collect feedback through other channels (email, forms) and iterate on the page.

Published pages and SEO

Published pages are accessible to search engines by default. The page title becomes the HTML title, and the first paragraph serves as the meta description. If you do not want a published page indexed by search engines, consider:

• Adding a noindex directive through your reverse proxy or CDN configuration
• Keeping the page unpublished until it is ready for public access
• Using a short-lived publish for targeted sharing, then unpublishing

Best practices

• Review before publishing — double-check the content for accuracy, confidentiality, and formatting before generating the public link.
• Do not publish sensitive information — publishing makes content accessible to anyone with the URL. Ensure no internal data, credentials, or confidential material is included.
• Track published pages — maintain a list of published pages so you can review and unpublish them when they become outdated.
• Use descriptive titles — the page title appears in the browser tab and when the link is shared on social media or messaging platforms.
• Keep content current — published pages that are stale or incorrect reflect poorly on your team. Update or unpublish pages that are no longer accurate.

Related pages

• Manage Pages — Page creation and management
• Page Access Control — Permissions and sharing
• Page Editor — Rich text editing guide
• Wiki — Structured knowledge base mode