Space Membership
Last updated: June 29, 2026
A Space Membership is a record of which SpaceRoles a person holds in a given Space. One person can belong to several Spaces, and the permissions may differ per Space, so each combination of a person, a Space, and a set of permissions corresponds to one Space Membership. Unlike Organization Membership, which brings in a new person by inviting them by email, a Space Membership adds an existing user with a user reference and grants permissions through roles (an array of SpaceRole references). It is not an email invitation.
You read the list of Spaces you belong to with GET /me/space-memberships. If you also send include=1, the details of the Space it points to are included in the response.
Resource structure
The following is the single-read response for one Space Membership. sys (system properties) holds the user (user) and the Space (space) this membership points to, and it has the body property roles (the set of permissions).
{
"sys": {
"id": "3trmXRM3RqbgSnifyg7PAm5memEx0",
"type": "SpaceMembership",
"space": { "sys": { "id": "tcq4V2Xb", "type": "Refer", "targetType": "Space" } },
"user": { "sys": { "id": "3p4tcFbQRwz503VXdtHXNI5dZH5TVB", "type": "Refer", "targetType": "User" } },
"createdBy": { "sys": { "id": "3p4tcFbQRwz503VXdtHXNI5dZH5TVB", "type": "Refer", "targetType": "User" } },
"createdAt": "2026-06-14T14:56:04.737Z",
"updatedBy": { "sys": { "id": "3p4tcFbQRwz503VXdtHXNI5dZH5TVB", "type": "Refer", "targetType": "User" } },
"updatedAt": "2026-06-14T14:56:04.737Z",
"version": 1
},
"roles": [
{ "sys": { "id": "3trmXRM3RqbgSnifyg7PAlm4FWTPQ8", "type": "Refer", "targetType": "SpaceRole" } }
]
}Key properties:
space: ARefer<Space>that points to the Space this membership belongs to.user: ARefer<User>that points to the user of this membership. The user you add as a member is bound here.roles: The set of permissions this user has in the Space. It is an array ofRefer<SpaceRole>pointing to SpaceRoles, so one member can hold several SpaceRoles at once.
System properties (sys) and body
Every Space Membership carries common system properties in the sys object. space, user, createdBy, and updatedBy are in the Refer shape ({ "sys": { "id", "type": "Refer", "targetType" } }).
| Property | Type | Description |
|---|---|---|
id | string | Unique resource identifier. |
type | string | Resource kind. For a Space Membership this is always "SpaceMembership". |
space | Refer<Space> | The Space this membership belongs to. |
user | Refer<User> | The user of this membership. |
createdBy | Refer<User> | The user who created it. |
createdAt | string (date-time) | Creation time. |
updatedBy | Refer<User> | The user who last updated it. |
updatedAt | string (date-time) | Last update time. |
version | integer (≥1) | Resource version. It increases by 1 with every change. |
Body properties:
| Property | Type | Description |
|---|---|---|
roles | Refer<SpaceRole>[] | The member's set of permissions. An array of Refer pointing to SpaceRoles, holding 1 to 3 entries. One member can hold several SpaceRoles. |
A Space Membership is a settings resource with no publishing concept. So unlike Content and Media, its sys has no publish, archive, or status, only version. The version increases each time you update the membership.
API
The base URL for all endpoints below is https://cma.weegloo.com/v1, and a Bearer token that authenticates against CMA is required in the Authorization header. Role updates (PUT, PATCH) must also send the X-Weegloo-Version header (the current resource's sys.version) for optimistic concurrency control. Adding a member (create) and delete do not have this header.
Related documents
- SpaceRole: The definition of the SpaceRole (the set of permissions) you put in
roles. - Space: The Space this membership belongs to.
- Organization Membership: Members and roles at the Organization level.
