Protected report publishing

Share a full report with people who were not there, without making it public. Publish to your own Cloudflare account, or host it privately on Proofline. Both require sign-in.

Uses your own account, or a Proofline connection in preview.

Needs
A Cloudflare account with a Pages project, an Access application and an API token
Or
A Proofline connection for hosted reports (preview)
Help
Set up protected publishing

When to use it

Use it when the developer needs the screenshots, video and full timeline, not just the issue text. Publishing is also the step that makes one-click GitHub issues possible, since each issue links to its report.

How Cloudflare reports are protected

Setup in brief

Create a Direct Upload Pages project, protect its preview deployments with an Access application and an Allow policy, then enter the account ID, a scoped API token, the project name, the Access application ID and team domain in Settings → Publishing. Verify Access & save checks the configuration. The setup guide has every step.

Proofline hosted reports

With a Proofline connection (preview), you can host a report on Proofline instead of setting up Cloudflare. Only workspace members you select can open it, and you can invite other readers, who sign in with a free Proofline account. A hosted report stays until you delete it, within your workspace’s storage quota.

Limits and costs

Record your next bug instead of describing it

Session Recorder is free and open source under the AGPL-3.0. Recording and ZIP export need no account. AI, transcription and publishing are optional: use your own providers, whose charges apply, or use credits with the optional Proofline connection preview when it reaches your installed version.

Get started with Proofline