Skip to main content
A job, a check or a session you created can be shared two ways. By email, the person signs in with that address and reads the run, in the dashboard or under --scope shared in the CLI. By link, anyone holding the link reads the run without an account.
--email sends one plain-text email with the run’s address; an address with no account gets a sign-up link that lands on the run, unless that address is already on the waitlist or holds an invite, and then it keeps that path. --link turns on the run’s unlisted link and prints it, the same one every time.
shares prints who the run is shared with. unshare --link turns the link off at once; a later share --link prints a new one. The same verbs exist for checks and sessions: evolve check share, evolve session share. In the SDK: jobs().share(id, { link: true }), jobs().share(id, { emails: [...] }), jobs().unshare(id, { ... }), jobs().shares(id); the same three on checks() and sessions(). In the browser a shared job opens on the run, its trials and each trial’s trace, read only. A shared session opens on its transcript, with a download of the trace. A shared check offers its archive. Nothing on a shared page can stop, retry or delete anything, and the browser replay of a session is not part of a link.

​
In the dashboard

SHARE sits on a job’s page, on a task check’s trace opened from the job’s CHECK tab, and on a session’s trace under Traces. It opens the dialog: type an address and INVITE, or under General access turn on Anyone with the link and copy it. Turning it off stops the link at once. Only the run’s creator sees SHARE. Runs shared with you by email are listed under SHARED WITH ME on Traces.

job reference

job share, job unshare, job shares and their flags.