Sharing and forking

The unit you share is a version, not a whole setup. You pick one save, you get a link, and whoever opens it gets their own copy in their own library. Theirs stays untouched, and so does yours.

Sharing a version

Save a version first. A setup with nothing saved has nothing to share, and the console says so directly: Save a version to share this.

Then, from the version row or from the setup:

aq share <name|id>

That returns a link to one saved version of the setup.

Controlling who can reach it

Each version has a visibility setting. Change it, along with the label and description, with:

aq edit-version <id>

The label and description are what someone sees before they decide to fork, so they are worth filling in on anything you send outside your own team.

Forking a link someone sent you

Paste the link into Paste a share link on the Setups page or the New setup screen. From the terminal:

aq fork <share-link>

You get a new setup in your own library, disk and history included. Nothing about the original changes, and the person who shared it does not get billed for your copy.

Setups that others have shared with you appear under Shared with me in the console.

Forking your own setup

The same mechanism works on your own work. On the New setup screen, Start from a saved setup forks one of your existing setups, disk and history included. This is the right move when you want to try something risky without touching the setup that currently works.

What it costs

A fork holds its own copy of the data, so it bills its own $0.02/GiB per month while it exists. Forking a large setup to try one small change and then leaving it around is the usual reason a bill drifts up. Delete the fork's versions when you are done with it.