Skip to main content
Sharing sends a link by email that gives the recipient access to one specific thing: an agent, a single run, or a workspace’s runs list. This is how you show a stakeholder the evidence behind a run without walking them through the whole product, and how you bring a new colleague into a workspace around real work rather than an empty invitation.
Sharing is a web UI feature. There is no jstm share command.

​
What you can share

​
How it works

  1. You choose a target and enter an email address.
  2. The recipient gets an email with a link. The link is tied to that address and expires in 7 days.
  3. Opening it shows a preview — who invited them, which workspace, and what the target is — before they commit to anything.
  4. Accepting adds them to the workspace as a member and takes them to the object.
If the recipient is already a member of the workspace, there is nothing to accept. They go straight to the object.
Accepting a share adds the person to your workspace as a member. They get access to the workspace, not only to the shared object. Share deliberately.

​
Who can share

You must be a member of the workspace that owns the object. To share something built in your personal workspace, move it to a team workspace first:
See Organize and publish agents.

​
Managing shares you’ve sent

You can see the shares you’ve sent, and for each one:
  • Resend — sends the invitation email again and resets the 7-day expiry.
  • Revoke — invalidates the link. An unaccepted share stops working immediately.
Revoking a share does not remove someone who already accepted it. To remove their access, remove them from the workspace:

​
Sharing inside your organization

For an agent that a whole organization should be able to find and use, visibility is a better fit than a share:
Any workspace in the organization can then discover it with jstm agent search and install their own copy, running it with their own credentials. See Visibility and discovery. Use sharing for a specific person and a specific thing. Use visibility for a capability the organization should be able to reuse.

​
See also