remove_team_member

Purpose

Removes a collaborator from a team. They lose access to every project and setting scoped to it immediately; their own Subscriby account is untouched.

The team owner cannot be removed — ownership is not a membership row.

Not tier-gated, unlike inviting. A creator whose tier lapsed with collaborators still attached has to be able to remove them; gating that would turn a downgrade into a permanent grant. See what the tier gates.

Only works on someone who has accepted. Somebody still holding an unaccepted invitation has no membership row to remove — use cancel_team_invitation for those. Using the wrong one returns RESOURCE_NOT_FOUND rather than doing something surprising.

Required ability

team-member:remove

Input schema

{
  "type": "object",
  "properties": {
    "team_id": { "type": "string", "description": "UUID of the team." },
    "user_id": {
      "type": "string",
      "description": "UUID of the collaborator to remove."
    }
  },
  "required": ["team_id", "user_id"]
}

Output shape

{
  "data": {
    "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86",
    "user_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",
    "removed": true
  }
}

Emits team.member.removed.

Example prompts

"Remove [email protected] from the Research team — they've left."

Failure modes

AUTHENTICATION_REQUIRED — no authenticated user on the request.
TOKEN_MISSING_ABILITY — token lacks team-member:remove.
RESOURCE_NOT_FOUND — no such team, or user_id is not a member. The owner also returns 404.

cancel_team_invitation
invite_team_member
list_team_members — resolve the user_id first.
Team Members API