Sharing and Collaboration

What sharing does

You can share any run in your history with other people. For each share you choose who gets access, how much they may do, which output files they may download, and when access ends. You can change or revoke a share at any time from the Collaboration tab.

Two ways to share

Method	How it works
Public link	A URL of the form /shared/<token>. Anyone who has it can see the run summary and download the files you ticked, without signing in. Treat the link as a secret. Signed-in visitors can add it to their own workspace.
Specific user	A grant to one AutoData account. The run appears on that person's Shared with me list.

Permission levels

Each level includes everything in the levels above it in this table.

Level	API value	The recipient can
View only	read	See the run summary (name, source file, status, date, row and column counts, owner, note). Download the files you ticked. Read comments.
Can comment	comment	Also post comments and delete their own comments.
Can edit	edit	Also rename the run, clone its configuration into a new run of their own, and use it as the parent of their own inference or retraining runs. Download every output file and see the full run record, including its configuration.

No level lets a recipient delete your run, re-share it, or change its files. Anything a recipient starts from your run (a cloned run, inference or retraining) is their own run and is billed to them. If an editor renames the run, the new name is what you and everyone else see too.

Anonymous link visitors can only view, whatever level the link carries. To comment or edit through a link, a visitor signs in and adds the link to their workspace. That creates a grant at the link's level.

Creating a share

1. On the Collaboration tab, click + Share Session.
2. Pick the run.
3. Choose Public link or Specific user. For a user, find them by email or name (see below).
4. Pick the permission. The default is View only.
5. Optionally tick the output files to share. With nothing ticked, the recipient sees the summary only. Files you do not tick cannot be listed or downloaded.
6. Optionally set an expiry date and time. It must be in the future, and it applies to links and direct shares alike.
7. Optionally add a note for the recipient, then click Share. For a link, copy the URL that appears.

If you share again with someone who already has a direct share of the same run, their existing share is replaced with the new settings rather than duplicated.

Finding a recipient

AutoData never lets you browse its user directory.

• To reach someone new, type their full email address. This is an exact match, and it finds at most one account.
• To find a contact, type part of their name. Contacts are people you have shared with, or who have shared with you.
• Leave the box empty to see your most recent contacts.

Results show a name and a masked email address, five at most.

Managing your shares

Shared by me lists every share you created, with its recipient, permission, expiry and creation date. From each row you can:

• Copy the link (link shares only).
• Edit the share: permission, expiry (clear it for no expiry), shared files and note. The recipient and share type are fixed. For a link, changes to permission, expiry and files also apply to everyone who added it to their workspace. Changes to the note do not.
• Revoke the share. This takes effect immediately. Revoking a link also removes it from every workspace it was added to.

Expired shares stay listed, marked Expired, until you revoke them. To restore access, edit the share and set a new future date.

Comments

Each shared run has one comment thread. The owner and everyone with live access to the run can read it. Recipients with Can comment or Can edit can post. A comment can be up to 2,000 characters. Authors can delete their own comments, and the owner can delete any comment. Comments are kept when a share is revoked.

The shared link page

The link page shows who shared the run, its status, the file name, row and column counts and date, the ticked files, the owner's note, the permission, and when access ends. The button depends on who is looking:

• Signed-out visitors can sign in and come back to the same page.
• Signed-in visitors can Add to my workspace, or open the run if they already added it.
• The owner can go straight to the Collaboration tab.

Adding the same link twice does nothing new. Adding a link never lowers access you already have through a stronger direct share.

API

These routes accept a session cookie or an API key, under /api/v1/shared-sessions. The older /api/shared-sessions spelling also works.

Method and path	Purpose
GET /api/v1/shared-sessions	Shares you created
GET /api/v1/shared-sessions/received	Shares you received
POST /api/v1/shared-sessions	Create a share. Body fields: session_id (required); shared_with_id (omit for a public link); permission (read, comment or edit; default read); shared_files (list of file names); expires_at (ISO-8601); note.
PUT /api/v1/shared-sessions/<share_id>	Change permission, expires_at (null means it never expires), shared_files or note
DELETE /api/v1/shared-sessions/<share_id>	Revoke a share
GET /api/v1/shared-sessions/access/<token>	Public link summary. Returns 404 if the link is unknown or revoked, 410 if it has expired.
GET /api/v1/shared-sessions/access/<token>/download/<file>	Download a shared file through a link
POST /api/v1/shared-sessions/access/<token>/join	Add a link to your workspace (requires sign-in)
GET or POST /api/v1/shared-sessions/by-session/<session_id>/comments	Read the comment thread, or post a comment with {"body": "..."}
DELETE /api/v1/shared-sessions/by-session/<session_id>/comments/<id>	Delete a comment
GET /api/users/search?q=	Find a recipient