Subshell Docs

Share a node

Let other users run subshells on your node, and decide how much of the machine's management they take on.

Before you start

You manage sharing as the node's owner, or as someone the owner gave Manage to. Recipients need accounts on the same server.

Access levels

Every grant picks one level, and the levels stack: each includes the one below it.

LevelWhat it grants
ViewSee the node and its status, and launch your own subshells on it.
View + editViewing, plus node configuration: reading its logs and runtime details, flipping debug logging, restarting its daemon, and sending it an update.
ManageEverything an owner can change about the machine: sharing itself, renaming, maintenance, directory rules, key rotation, repointing, stop and uninstall, the SSH switches and SSH trust re-pairing, the web previews and virtual displays switch, and the cross-agent guidance. It never reaches three things: transferring ownership, deleting or re-registering the node, and file transfers. A key (an admin mints them under Settings → Server Settings → API keys) can grant View or View + edit, never Manage.

Any level, even View, lets the grantee launch their own subshells there. Management controls stay out of View and View + edit; hand someone Manage only when you mean them to run the machine.

Choosing Everyone with Manage is the widest grant the ladder offers: it puts this machine's management in the hands of every signed-in account, including ones created later, until you change it. That's a deliberate option rather than a guard gap, but most owners mean named people.

Grant access

  1. In the server dashboard's sidebar, choose Settings → Nodes, open the machine’s ⋯ menu, and choose Share. You can also select the machine and choose Share at the top of its Overview page.
  2. Choose named users or the available instance-wide grant.
  3. Pick each grantee's level and save the permissions.
  4. Ask the recipient to confirm the node is available in their launch picker.

Sharing never moves ownership. The owner keeps the right to hand the machine over, and it's the only account that can (see Transfer a node).

Execution consequences

Shared OS account

Sessions launched by other users run under the node's execution account. They can access files and credentials that account can read.

A directory allowlist limits launch locations, not later filesystem access. Use a dedicated account or machine when projects or credentials require stronger separation.

The session created by another user belongs to that user. Node sharing and subshell sharing are separate permissions; sharing the machine doesn't make every session on it visible to every user.

Revocation

Remove the grant to stop future access through the node share. Use maintenance if you need to stop running sessions before working on the machine. A Manage grantee keeps managing the machine until you revoke them, so a departure is a shares edit, not a password reset.

Next steps

See Transfer a node, Directory restrictions, Node maintenance, and Access model.

Edit on GitHub

Last updated on

On this page