Skip to main content
Fetch My Membership
Returns the acting user’s own standing on a workspace: the token’s user, or the user a service key names in actingUserId. me in the path always means that user. The response is the same record Fetch Member Standing returns for another user, and the same shape as one roster row. Any signed-in user may call it for any workspace. It is not gated by roster visibility: a user with no relation to the workspace gets 200 with reasons: [], so “am I a member here?” always has an answer. Your own access is never fenced — capabilities, permissions, rank and relativeRank are always present.
Your own membership is /workspaces/:workspaceId/members/me: GET to read it, PATCH to edit your title, DELETE to leave. The /workspaces/:workspaceId/members/:userId routes (read, edit, remove, remove from subtree) act on other members and refuse your own id with 400 workspace/own-member-id.

Path Parameters

string
required
The workspace UUID.

Query Parameters

string
Service keys only, and required with one: the user whose standing is returned. A key that names nobody is refused with 400 workspace/missing-user-id. A user token always acts as its own user and must not send it (400 workspace/acting-user-not-allowed). See Acting on behalf of a user.

Response

  • reasons — structured { type, viaWorkspaceId? } entries; viaWorkspaceId appears on ancestor-owner / reach-holder entries only. Empty when the user has no relation to the workspace.
  • capabilities — the resolved set (direct + reach + ownership). view is implied by every other capability. Empty when the user has no relation.
  • permissions — per-node (the direct membership on this workspace only; may be empty).
  • rank — the direct-membership rank, or null when the user holds no member row here (an owner, an ancestor-owner or a reach-only holder).
  • relativeRank — 0 when the user holds a member row here (they are measured from themselves), null when they don’t.
  • title / metadata — from the direct member row; null / {} without one.

Error Responses

A service key sent no actingUserId. me is the acting user, so the key must name one.
A user token sent actingUserId, even naming its own user. Only a service key names the user it acts as; a user token always acts as its own user.
A GET takes every field, actingUserId included, in the query string.
Returned when a service key names an actingUserId that isn’t a user in this project.
No workspace with this id exists in this project.
See also: useFetchMyWorkspaceMembership · Fetch Member Standing · Read Authority