OrganizationMemberResponseDto

Example

JSON

{
  "id": "string",
  "identity": {
    "id": "string",
    "email": "string",
    "first_name": "string",
    "last_name": "string"
  },
  "status": "active",
  "source": "added",
  "joined_at": "2026-04-20T12:00:00.000Z",
  "deactivated_at": "2026-04-20T12:00:00.000Z",
  "roles": [
    {
      "id": "string",
      "role": {
        "id": "string",
        "name": "string"
      },
      "node": {
        "id": "string",
        "name": "string",
        "node_type": "string"
      },
      "effective_from": "2026-04-20T12:00:00.000Z",
      "effective_to": "2026-04-20T12:00:00.000Z",
      "version": 0
    }
  ],
  "version": 0
}

Properties

8 properties 7 required

id string Required

The membership id.

identity OrganizationMemberIdentityDto Required

status enum Required

`active` while the identity belongs; `deactivated` once removed, kept for the organization's history.

Enumactivedeactivated

source enum Required

How the membership began: added by an administrator, an accepted invitation, single sign-on, directory sync, or the organization's own creation on sign-up.

Enumaddedinvitationssodirectory_syncsignup

joined_at string Required

When the current membership began.

format: date-time

deactivated_at string Optional

When the member was removed; null while active.

format: date-timenullable

roles array of OrganizationMemberAssignmentDto Required

Every role assignment the member holds in the organization, the organization node first, then beneath it. Empty for a member who holds none.

version number Required

The membership's version.

Was this page helpful?

Tell us how we can improve this guide.