Share the right version with the right people

Before sharing Launch plan, decide who should read it: a workspace member or someone without an account. dtxWiki provides separate internal and public links.

Share with a workspace member

1. Open the Context page and choose Share.
2. Under Workspace link, choose Copy workspace link.
3. Send the link through your usual communication channel.

The recipient must sign in and have workspace access. Copying a link does not add a member or bypass their role. Workspace Viewers read the published page version; authorized Editors may see draft states they are permitted to read.

To add a person, an Owner uses Members and access. Membership shares the workspace according to the role, rather than only granting access to the page whose link you copied.

Publish one page to the web

Publish in the editor creates the workspace's published version. Publish to web separately enables an anonymous, read-only page URL.

1. Publish a page version and open Share.
2. Choose Preview published version and inspect the exact content, including images, identifiers, and quoted material.
3. Read the anonymous exposure scope.
4. If the workspace is not Public, an Owner must use a browser session and confirm the acknowledgement that anyone with the link can read the page.
5. Choose Publish to web, then Copy public link.
6. Open that public link while signed out to check what a visitor sees.

Workspace setting	Anonymous page sharing
Public workspace	Editor/Owner sharing can make the selected published page publicly discoverable.
Non-public workspace	A browser-session Owner can explicitly expose a selected published version through an unlisted direct URL.

“Unlisted” is not “secret.” Anyone who obtains the URL can read and forward it, and it may be indexed. A public page does not expose the complete internal workspace, its draft history, or all Library originals.

Keep public and draft versions distinct

Visitors receive the authorized published snapshot, never a newer unpublished draft. Internal publishing and public exposure are separate state changes. After publishing a replacement or changing workspace access, check the live public page and Share state again; do not assume an old acknowledgement grants every later version anonymous access.

For non-public workspaces, the exposure acknowledgement is tied to the expected published version. If that version changed before sharing, inspect the current published snapshot and confirm again.

Use Unpublish from web to remove anonymous access. The internal published page remains available to workspace members. Previously downloaded copies cannot be recalled by changing a link's access.

If the link does not work

• Check whether you sent the internal workspace link or the public link.
• Publish a page version before enabling web access.
• Check the role; starting anonymous exposure from a non-public workspace requires Owner authority.
• If copy is blocked by browser permissions or HTTP, select the link and use Ctrl+C.
• A public reader's “Page not available” can mean private, archived, unavailable, or nonexistent content; it does not reveal private details.

See Privacy and security before publishing sensitive material.

Implementation reference: share control, public exposure checks, exposure lifecycle.