VISIBILITY
Start with a private draft. Share it deliberately.
Keep a draft to yourself, open it to Workspace members, or publish it for anyone to view. Choose the audience before you share the link.
View the sampleILLUSTRATIVE SAMPLE · THE REVIEW GAP
Choose the audience as part of the publish action.
This sample is a single uploaded HTML file. It shows the workflow shape; it is not a customer artifact or a production approval.
- Without a review artifact
- The same artifact may begin as a private draft, move into a team review, or become a public example. The audience must be explicit before the URL is shared.
- With the versioned workflow
- Public allows anonymous viewing. Workspace requires active membership in the owning Workspace. Private is limited to the current private owner and is the default for a new Slide.
UPLOADED HTML SAMPLEOpen full sample
PUBLISHING SEQUENCE
One artifact. Four explicit decisions.
led publish ./artifact.html --visibility workspace --json- 01
Name the intended audience
Decide whether the artifact is for anyone, active Workspace members, or only its current private owner.
- 02
Select a supported visibility
Use public, workspace, or private. Knowing the URL alone does not bypass the access boundary.
- 03
Publish with the visibility in the command
Keep the access decision beside the artifact path instead of relying on a separate hosting console.
- 04
Change it deliberately
When updating an existing Slide, omitting --visibility preserves its current visibility.