For security teams
Share scan output and assessment write-ups as sandboxed, expiring links, and understand exactly what the rendering and visibility model does before you approve it.
The situation
You are either publishing findings that need controlled distribution, or you are the person being asked to approve a tool that renders untrusted HTML. Both need the same thing: a clear account of how the document is isolated, who can reach the link, and how access ends.
What you are publishing
- Assessment write-ups
- Findings with severity, evidence, and remediation guidance, shared with a specific team for a limited window.
- Scanner output
- Dependency, container, or static analysis reports rendered as a document rather than a JSON dump.
- Incident timelines
- A reconstructed sequence with supporting detail, shared during an active response and revoked when it closes.
What matters most here
Sandboxed rendering is the default
Artifact HTML renders in a sandboxed context rather than with the privileges of the surrounding application. This is the whole reason a generated document should not be opened straight from a download.
Noindex by default
Artifact and project pages are unlisted and noindex, so a findings document does not become a crawlable page.
Revocation is immediate and explicit
Disabling a link stops access. Expiry does the same on a schedule. Both are owner actions, not support requests.
Source access is auditable
The original HTML remains downloadable by the owner, so what was published can be verified after the fact.
How the workflow runs
- 01Redact before publishing. Nothing here removes secrets from a document that contains them.
- 02Publish with private visibility on Pro when the audience is only you, or unlisted with a short expiry for a named team.
- 03Distribute the link through a channel you already trust for this class of information.
- 04Revoke as soon as the window closes rather than waiting for expiry.
- 05Keep the source copy for your own records.
The questions this team asks first
Is unlisted the same as access-controlled?
No, and treating it as such is the most common mistake. Unlisted means unguessable and noindex, not authenticated. Anyone who receives the URL can open it. If distribution must be restricted to named people, this is not the right tool for that document.
What stops a malicious document attacking a viewer?
Rendering is sandboxed and isolated from the application. That mitigates a large class of problems, but no sandbox is a guarantee, and it does not stop a document from containing misleading or hostile content. Read the sandboxing page for the specifics of the model.
Where does the HTML actually live?
Source HTML is stored in object storage with metadata in Postgres. Expired artifacts are removed by a scheduled retention process. The privacy page describes the processors involved.