Publish a public documentation Space

Make a Space public when its full documentation collection is intended for readers outside your account or team.

Review before publishing

Read the pages and navigation for internal details, credentials, customer data and links that require private access. Publishing is a Space-level decision; a folder name such as “Internal” is not an access control.

Confirm the overview explains the intended audience and that important pages contain finished content. Remove empty placeholders from the reader journey.

Configure public access

Open the Space's settings, enable public visibility and configure the public slug using the controls provided. Save, then open its public URL in a browser session that is not signed in.

Check that the correct pages, images and links are visible. Public readers get a reading experience; publishing does not grant them permission to edit the Space.

Maintain public links

Avoid changing an established public slug casually. Public page URLs include the Space slug and the folder/page path. Moving a page or changing its URL settings changes its canonical location; verify existing links and redirects after reorganizing. Deleting a page can make a saved link unavailable.

If you return the Space to private visibility, check the public URL again. Keep copies or exports you have already shared in mind: changing visibility cannot recall content someone already downloaded.

Public pages support Copy page and Open in AI. Ask AI has separate publisher-entitlement requirements.

For internal collaboration, use team access and keep the Space private until external publication is intended.