Skip to content

Share a computer

Being in an organisation opens nothing by itself. Each computer has an access list, and a person gets in only when that list names them, directly or through a team. Your role in the organisation never overrides the list.

Computer Who can open it
Your own personal computer You.
Someone else’s personal computer Nobody, owners and admins included, until its owner gives that person access.
A shared computer Organisation owners and admins, with every session. Everyone else once an owner or admin gives a person or a team access.

A billing member can’t open any computer.

An owner or admin finds another member’s personal computer in a collapsed section, Other people’s personal computers, labelled “not shared”, with a quiet Ask … to share link. They can’t open it, answer its approvals or read its sessions. A member doesn’t see it at all until its owner names them.

The owner opens it to a person from the computer’s access sheet:

  1. In Account, Computers, choose Who can open this on the computer.
  2. Under Give a person access, pick the person, a role, which sessions and how long.
  3. Choose Sign and give access and confirm with your passkey.

The access is signed on one of the owner’s own approved devices. No admin and no policy can sign it for them. A personal computer can be opened by named people only, at Driver or below. It can’t be given to a team or to the whole organisation.

An organisation can narrow this. If its policy keeps personal computers to their owners, the row says “Your organisation’s policy keeps this personal computer to its owner.”

An owner or admin opens a shared computer as Admin, over every session. That is the sentence you read at the terminal when you enrol it: every org owner and admin can read every session on this computer and answer its approvals.

A member starts with nothing. Their row reads No access and Ask an admin. An owner or admin can then give access to:

  • one person
  • a team
  • all organisation members, if you want that

Owners and admins can also remove the admin entry from a single computer, from the same sheet. Organisation owners and admins then stop reaching it, unless a person or a team entry still names them.

Signing in is enough for your browser. A shared computer checks your sign-in and its access list, and lets the browser in at the role the list gives you, with nothing else to approve. If your organisation’s policy has admins accept each new browser, an admin accepts it first. A computer on a remotxai version older than 0.3.23 doesn’t let a browser in on sign-in yet: the app names it and asks for remotxai upgrade there.

Role What the person can do
Viewer Watch sessions. Nothing else.
Approver Watch and answer approvals.
Driver Watch, send prompts and start sessions.
Admin Everything, including changing the computer’s settings.

On a personal computer the highest role is Driver.

Each entry has a visibility:

  • Only sessions they start. The default for people, teams and all-members entries. The person sees the sessions they started and nothing else.
  • All sessions on this computer. You choose this on purpose.

With the first, the person’s session list, counts, needs-you badge, approvals and search cover their own sessions only. The computer row says “You see only sessions you started”. Sub-agents belong to whoever started their parent session.

Some sessions have no starter: ones started at the computer’s terminal or with the command line, and older sessions. Only an All sessions entry, or the owner of a personal computer, sees those. An admin hands one to a person with Assign to in the session.

Starting a session is allowed with either visibility, and the new session belongs to the person. The computer’s terminal, browsing files outside a session, adopting a session and computer settings need All sessions.

Visibility is a limit inside remotxai and nothing more. Every session runs as the same user on the computer, so a session can read files another session wrote. The access sheet says so.

Before you sign, the sheet writes the grant as one sentence:

  • “Ana can read and drive sessions they start on build-box”
  • “Ana can read and approve every session on build-box until 30 November 2026”

The verb is read, read and approve, read and drive, or administer. It follows the role you picked. Check it before you confirm.

An owner or admin chooses Ask the owner on a member’s personal computer. A member with No access on a shared computer asks an admin. Asking changes nothing by itself. The owner or admin sees your request under Asking for access with Review, which fills the form with what you asked for. Nothing changes until they sign. Dismiss removes the request.

If you ask too many times, wait an hour and try again.

Choose Remove on a person, a team or the admin entry. The computer closes their connection within seconds. A personal computer’s owner can remove any entry at any time.

If the device that signed the list is revoked, the people on it can’t open the computer until an owner or admin signs the list again. The sheet shows Sign the list again.

An entry can run out. Pick 7 days, 30 days or Until revoked when you give access.