Delegations

Delegations let an authenticated user delegate participant membership to another active user. They are stored as runtime overlays and do not rewrite provider-synced directory records.

Scopes

Delegations support two scopes:

Scope	Behavior
all_participants	Delegates all current participant memberships for the delegator.
participant	Delegates one specific participant membership.

Participant-scoped delegations require participant_id.

Timing

A delegation can be:

• active
• upcoming
• expired
• revoked

Set starts_at and ends_at when the delegation has a known coverage window. Open-ended delegations omit ends_at.

Authorization

Admins can manage all delegations. Project owners can manage participant-scoped delegations for participants in projects they own. Other non-admin users can manage only their own delegation context when their login email maps to a direct or indirect participant directory association.

Example

{
  "delegate_user_id": "drec_...",
  "delegator_user_id": "drec_...",
  "scope": "participant",
  "participant_id": "part_...",
  "starts_at": "2026-05-27",
  "ends_at": "2026-06-27"
}