Share links and access requests

The portal screens are in development. Their words and layout may still change; the commands behind the buttons are already built.

You share a release with its share link. A link is an address, not a permission. IDs and paths here are examples.

Every release has a share link, which looks like https://app.example.org/r/r-0139.

Where to copy it. [Copy share link] under “Just released” right after a release; “Released by me” and “Visible to me” on the [Releases] screen; and [Copy link] on the share page itself.
Who can open it. “Whoever gets the link still needs permission to open it.” The system checks each time it is opened.
Your installation only. Only people with an account on the same installation can open it. There is no way to send a release to people outside.
When signed out. Someone who is not signed in is asked to sign in and then taken back to the link.

Copying a link runs no command, so it does not appear in the console.

What the link shows

Previews. Images (png, jpeg, gif, webp), the first rows of tables (parquet, csv, tsv) and metrics (json), right on the page. Model weights show their file details only.
Summary. Created by, created, workspace, data used, who can see and the reproduce script; for a corrected release, what it replaces or what replaced it.
Sources. A picture of the data and releases it came from. Anything you may not see appears without a name, as “Data you cannot see”.
Re-run check. Every release shows “Not re-run yet” today: “Not yet run again to check.” Also: “The reproduce command and the environment at the time are saved.”
[Download]. “Downloads are recorded”. Views and previews are recorded too.

When you cannot see it

Someone without access who opens the link sees this instead of the release: “To see this release you need these roles, at least one from each line.” Each line under “Roles needed” is marked “Met” or “Not met”.

Press [Ask an admin], and if you like, say why under “Note to the admin (optional)”.

Command console App in development

$ release request-access r-0139 Done

Requested access: r-0139

A note adds --note to the command. This is an example, drawn from the app in development.

The admin gives you a role, widens who can see that one release, or declines with a note. “When an admin handles it, open this link again.” Your requests and their outcome are on the “Access requests” tab of the [Releases] screen.

If you see “Only admins can see this release now.”, nobody currently has a role that may see its source data.

Using a release in your own work

A release you can see can become data in one of your workspaces. Look at how it changes who can see the results before you add it.

[Add to workspace]. Choose the workspace and it is added at once.
[Create workspace]. Starts a new workspace that uses this release.
Paste it to Claude. Pasting the link to Claude in a workspace turns it into a request to add the release; it is added once you approve.

An added release appears read-only under /data/releases/, and whatever you release next lists it among its sources.

When permissions change

Because the link is checked every time, someone whose access is revoked can no longer open it, at once. Files already downloaded cannot be taken back.

The release lists

The [Releases] screen has three tabs:

Released by me: your own releases. [Release new version] here releases a corrected one.
Visible to me: colleagues' releases you may see.
Access requests: the requests you made, and what happened to them.