> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Remove member

> Remove a member from this workspace.

`remove_member`

Remove a member from this workspace. Their keys stop working on the next request, because every principal re-reads membership per request. The last owner cannot be removed.

<Note>Hosted MCP registration verified. These schemas describe the development contract; confirm supported inputs with tools/list. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL\_API\_URL; production does not expose these command routes.</Note>

| Access           | Behavior                                                   |
| ---------------- | ---------------------------------------------------------- |
| `projects:write` | Writes or admits work; can change or remove existing state |

Reading saved data does not start a verification job. Mutations can change saved records or access; the effects below apply.

## Example request

Connect through [MCP](/guides/connect-mcp), [CLI](/guides/connect-cli), or [HTTP](/guides/connect-http). Replace example identifiers with records from your workspace.

<CodeGroup>
  ```json MCP theme={null}
  {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "remove_member",
      "arguments": {
        "userId": "user_example"
      }
    }
  }
  ```

  ```bash CLI theme={null}
  linktrail call remove_member --args '{"userId":"user_example"}'
  ```

  ```bash HTTP theme={null}
  curl "$LINKTRAIL_API_URL/v1/commands/remove_member" \
    -H "Authorization: Bearer $LINKTRAIL_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{"userId":"user_example"}'
  ```
</CodeGroup>

## Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in `structuredContent` and in a text content block; generic HTTP and CLI return the JSON result directly.

```json theme={null}
{
  "user_id": "user_example",
  "removed": true
}
```

## Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

| Field    | Type   | Presence | Meaning and constraints                                                                       |
| -------- | ------ | -------- | --------------------------------------------------------------------------------------------- |
| `userId` | string | Required | Identifier of the user returned by its create or list operation. minLength: 1; maxLength: 128 |

### Validation and omitted values

The last owner cannot be removed. Current membership is checked again on future authenticated requests.

## Output fields

Fields inside optional or nullable parents apply only when that parent exists. [Common schema conventions](/reference/schemas) explain evidence states, empty lists and extensions.

| Field     | Type    | Presence | Meaning and constraints                           |
| --------- | ------- | -------- | ------------------------------------------------- |
| `user_id` | string  | Required | user id recorded for this result.                 |
| `removed` | boolean | Required | removed recorded for this result. must equal true |

[Download input schema](/schemas/remove_member.input.json) · [Download output schema](/schemas/remove_member.output.json)

## Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict.

See [error recovery](/reference/errors) for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

## HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See [HTTP route details](/reference/http/routes).

| Method and route              | Success | Details                                       |
| ----------------------------- | ------- | --------------------------------------------- |
| `DELETE /v1/members/{userId}` | 200     | Remaining arguments go in a JSON object body. |

## Continue

[list\_members](/reference/commands/list_members)

Follow the [related workflow](/guides/connect-http), inspect [capability status](/capability-status), or return to the [command index](/reference/index).