workspace_member_list / _add / _set_role / _remove. CLI: rip workspace member list|add|set-role|remove.
A guest is an editor (reads, writes and shares) or a viewer (reads). Admin is never stored: it comes only from owning the workspace or being the owning team’s owner or admin. A guest reaches only the workspaces they are added to. To give someone every team workspace, add them to the owning team (POST /v0/teams/{team}/members, MCP team_add_member, rip team add), where each member is billed. Keep private work in a separate workspace.
Any member may list the members (read). Editors and admins, guest editors included, add, invite, change roles and remove people (share).
Auth: Authorization: Bearer tr_... (an account API key). {id} is the workspace id or slug (any case; a slug two of your workspaces share is 409 AMBIGUOUS_REFERENCE listing each candidate’s id).
How an invite works
- You add an email address. If no verified Tokenrip user holds it, the row is an invite:
status: "invited",accountId: null, and aninviteUrl. It grants nothing until it is claimed. - Tokenrip emails the address. The email names the inviter (the verified address of the person behind your account) and the access, links to the invite page (
inviteUrl), and gives a line the person can paste into an AI assistant. An address with no verified Tokenrip account gets fixed text only: the workspace’s name and yournoteare on the invite page, under your address, not in the email. Someone who already has an account gets the name and the note in the email. Nothing in the email or the link signs anyone in, soinviteUrlis safe to share. - The person signs in with the six-digit code Tokenrip emails to that address: in the browser, or through an agent following the setup guide. That sign-in claims every invite waiting on the address. There is no accept step. The row becomes
status: "member"with theiraccountId.
status: "member", inviteUrl: null). An add by address emails them that they were added; an add by alias or account id emails the account’s verified person only when it has exactly one and your account has one to send from.
GET /v0/workspaces/{id}/members
Every member and pending invite, oldest first. Owner and team access is not listed. Any member may read it. A viewer (no share) gets the people only: no invited rows, and id, email and inviteUrl are null on each row. A non-member gets 404 WORKSPACE_NOT_FOUND.
POST /v0/workspaces/{id}/members
Returns the member or invite row (
201). Needs share. membership is refused 400 INVALID_FIELD: “Everyone added to a workspace is a viewer or an editor; set role.”
- Adding someone again with the same role changes nothing, except that a pending invite is emailed again (at most once an hour). Adding them with a different role changes it.
- An add by address needs one verified person behind your account to send the email from (
NO_OPERATOR/OPERATOR_AMBIGUOUSotherwise). An add by alias or id without one goes ahead with no email. - Invite emails are limited per person, across all their accounts: by default 20 an hour, one per invite an hour, and one per address an hour. Past a limit an add is refused
RATE_LIMITED, except an add of an existing account by alias or id without anote, which goes ahead without the email. Removing an invite does not give its email back.
PATCH /v0/workspace-members/{member}
Body { "workspaceId"?: "<workspace id or slug>", "role": "viewer" | "editor", "why": "<goal>" }. Changes the role (role is required). Needs share. membership is refused as for an add. {member} is the row id from the list, which stands alone (its workspace is the row’s; with workspaceId the row must be in it), or, with workspaceId, an account id, an alias or an email address (URL-encoded). An address names the row of the person who holds it, on their primary account, or the row an add or invite by that address made; for a member on another of their accounts, use the row id. Returns the row.
DELETE /v0/workspace-members/{member}
Body { "workspaceId"?: "<workspace id or slug>", "why": "<goal>" } (why in the body, never the query). {member} as for PATCH. Removes a member, or cancels an invite. Needs share. Returns 204, also when the workspace has no row for a known account or address. Access ends on the next request; the account’s contributions remain.
GET /v0/invites/{id}
The public read behind the invite page (inviteUrl): the workspace name, the access (edit-shared or view-shared), and whether the invite is still active. It names the inviter’s and invitee’s addresses only for invites added by email address. Reading it claims nothing. It is used by the page; agents act on invites through the routes above.
Access changes
A change of role or a removal takes effect immediately. A change toviewer or a removal sends the account’s held tasks back to todo, withdraws its open proposals (task.withdrawn), and clears it (with its agents) as assignee or reviewer. It also disconnects the account’s paired browser views. Every change records the caller’s why, including on each stopped task. Someone who reaches the workspace as its owner or through the owning team keeps that access: changing or removing a leftover row of theirs changes nothing they hold.
When a guest joins the owning team, their row is removed in the same transaction, so leaving the team later does not revive the old access.