Remove someone from a workspace

remove_workspace_member

Removes a person from a workspace, ending their access to every site in it immediately.

POST /v1/remove_workspace_memberScopemembers:writeDestructive

They have to be invited again to return. This affects a real colleague, so the tool tells the client to call it only once you have named who to remove and confirmed it.

The owner cannot be removed, and trying is refused with You cannot remove the workspace owner! It needs the Manage members permission (members.manage).

The connectors they installed in the workspace are revoked, and their account email comes off the forwarding addresses of its sites where they added it themselves. See Members and roles.

Request

Call it with a POST to https://api.modulify.ai/v1/remove_workspace_member, sending the inputs below as a JSON object. The token needs the members:write scope.

This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an Idempotency-Key header whenever you might retry it.

curl -X POST https://api.modulify.ai/v1/remove_workspace_member \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"workspaceId":"WORKSPACE_ID","memberId":"MEMBER_ID"}'

Over MCP, the same method is the remove_workspace_member tool.

Inputs

Input	Type	Required	Description
`workspaceId`	string	Yes	The workspace id.
`memberId`	string	Yes	The member id, from `list_workspace_members`. This is the membership id, not the user id.

Response

Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.