Viewing & Sharing
Public Sharing Links
Public sharing lets you generate a unique link for any check that allows anyone with the URL to view the capture without needing a Crosscheck account. This is useful for sharing bug reports with external stakeholders, clients, or anyone outside your workspace.
How to Enable a Public Link
1
Open the check
Navigate to the check you want to share by clicking on it from the dashboard.
2
Click Share
In the check detail view, click the Share button located in the top-right area of the page.
3
Toggle the public link
In the sharing panel, toggle the Public Link switch to the on position. A unique URL will be generated immediately.
4
Copy and send
Click the copy icon next to the generated URL to copy it to your clipboard. You can then paste and share this link through email, chat, or any other channel.
Share panel with the public link toggle enabled and a copy button
What Viewers See
When someone opens a public link, they see a streamlined version of the check detail view that includes:
- The capture media (screenshot, video, or replay player).
- DevTools data (console logs, network requests, user actions).
- Page metadata (URL, browser, OS, and timestamp).
Team-specific information such as project details, internal comments, and workspace settings are not visible on the public view.
No account required
Anyone with the public link can view the check. They do not need to create a Crosscheck account or be a member of your workspace.
Deactivating a Public Link
You can deactivate a public link at any time by toggling the Public Link switch back to the off position. Once deactivated:
- The previously shared URL will immediately stop working.
- Anyone who tries to open the link will see an access denied message.
- You can re-enable the public link later if needed.
Be mindful of sensitive data
Public links are accessible to anyone with the URL. Before enabling a public link, review the check to ensure it does not contain sensitive information such as API keys, credentials, or personal data in the captured console logs or network requests.
Last updated: March 2026