Access model
Understand the permissions applied to people and machine credentials.
Ownership and grants
A subshell is private to its owner by default. The owner can grant view or edit to named users or Everyone on the instance.
View grants include output and live terminal viewing. Edit adds input, rename, restart, and termination. Neither grants deletion, re-sharing, or control of the owner's notification bell. SSH subshells have an additional restriction: only their owner, signed in to the dashboard, can send input. Edit grants and bearer credentials don't allow SSH terminal input.
Administrators
Administrators manage the instance. To view or control someone else's session, they need the same sharing grants as other users. Ask the owner to share it. Only the owner can delete the session, change its sharing, or control its notification bell.
Administrative endpoints require a cookie session with the admin role. Bearer credentials are refused there.
Pane credentials
A pane token resolves to its owner's identity for permitted operations, without administrator privileges or another user's sharing grants for session details and changes. It can act on other sessions owned by the same user.
The session list includes shared sessions that the pane's owner can see. If a session belongs to someone else, the pane may receive a 404 when it tries to inspect or change it, even though it appears in the list.
Node enumeration with a pane token follows the account it acts for: machines the account owns or that are shared with it, the server-host node included when its Everyone grant is on. Launching uses that same authority. A pane token doesn't gain the administrator's instance-wide list, though: list_nodes shows the non-admin set, so an administrator's token can launch on a private foreign machine only when something else names it, such as a saved preset. The Nodes page shows an administrator more machines than list_nodes does.
System keys
A system integration key belongs to the system service identity. It doesn't inherit the administrator's human resource ownership.
Node sharing permits execution on a machine; session sharing permits viewing or editing a particular session. They are separate grants. Node grants add a third level, Manage: it runs the machine's whole settings band, from sharing itself to stop and uninstall, but never takes ownership, deletes or re-registers the machine, or opens file transfers. Ownership moves only by the owner's own handover: neither a Manage grantee nor an administrator can start one, and an administrator's power to retire a machine never makes it theirs.
See also
Share a subshell, Share a node, and API keys.
Edit on GitHubLast updated on
