xTerminal

Docs

Roles and permissions

Owner, admin, and developer are people on the site. Workers and agents act through a key the developer mints.

A site has people, and it can have a worker. People have ranks in Team. A worker is not a Team rank. It acts with a site-scoped key. Invite people from Settings, Team (or Invite teammates at the end of signup).

People on the site

Owner

One owner per site. Signup creates that owner. They can transfer the site, manage billing, invite Team, add a site, and file Requests. They use the thread and the review card. They do not mint worker keys or edit the wake webhook.

Admin

Invited. Content, settings, Team, billing, and adding a site. They can mint worker keys. They cannot transfer ownership.

Developer

Invited only. They cannot sign up independently for a seat on your site. Content, worker keys, the site repository field, the wake webhook, and Ship to live. They do not manage billing, Team invites, or transfer.

How to invite

  1. Open Settings from the account menu, then Team.
  2. Choose Invite members.
  3. Enter one or more emails and pick Developer or Admin.

The product can mint a temporary password when you do not send one. That person is asked to set their own password on first login. You can change rank, resend, or remove from the same list. Seat limits follow the live plan: Foundation includes one developer seat, Advanced and Managed include two.

Workers and agents

A worker is the connected agent on that site. Admin or developer mints a key under Settings, Requests. The worker can read and update Requests for that site only. Speak of it as a worker or an agent. Do not name a bot brand in the product.

What owners never see

On a Request, owners do not see repo, branch, internal notes, or events marked not visible to the client. Worker keys and the wake webhook stay off the owner form. Owners still see status, messages they are allowed to see, preview, and the review card.

Transfer

Only the owner can transfer the site. Settings, Billing includes transfer. The other person must already have an account, and they become owner. The previous owner is stepped down to developer. There is one pending transfer at a time, and billing must be active.