Sharing a session

You can turn an Automate Browser session report into a public, read-only URL and send it to someone who has no TestKase account — a client, a contractor, a colleague on another team.

Creating a link

Open the session and click Share, in the header row next to End session. The dialog offers:

• Link expires — 7 days, 30 days, 90 days, or Never. The default is 30 days.
• Email the link to (optional) — a comma-separated list of addresses, up to 10. Leave it empty to just get a link.

The button reads Create link, or Create link & send once you've entered addresses. The new URL is copied to your clipboard automatically.

Below that, Active links lists every link currently working on this session, each with Copy and Revoke. Links you've revoked, and links that have expired, move to a separate No longer active list so you can see what used to exist without it cluttering the live set.

Rows under No longer active are a receipt, not a control: they carry no Copy and no Revoke button, because there is nothing left to copy that would work and nothing left to revoke. A dead link cannot be reinstated — if you need one again, mint a new one.

How links work

• The link carries a 22-character token. It is not guessable and it is not derived from the session id.
• Both expiry and revocation are enforced in the database on every request, so a revoked or expired link stops working immediately — there's no cached copy that keeps serving.
• The page is read-only. Nobody following the link can re-run, rename, or delete anything.
• A shared page cannot re-share — the Share button is hidden there, so a recipient can't mint further links.

Rate limiting

Anonymous access to a shared report is rate-limited to 30 requests per minute per IP. Normal reading never hits this; a scraper does. The limit counts only anonymous share-token traffic — signed-in members of your organization reading the same session are on a much higher limit, so a whole office behind one IP doesn't trip it.

Seeing colleagues' sessions

Separately from sharing, organization owners and admins can read sessions created by other members of their org from inside the dashboard. They don't need a share link for that.

What sharing does not do

These are real limits today, not oversights you should design around silently.

• A link is not locked to its recipient. Anyone who has the URL can open it, including someone it was forwarded to.
• You can't share a single test, or a whole build. The unit of sharing is one session.
• There is no PDF export, and no Slack or Jira embed.
• Mobile sessions can't be shared — including mobile-browser runs, which appear in the same Browser session list as desktop runs. Sharing covers desktop browser sessions only.