Delegations
A delegation lets one authenticated user delegate participant membership to another active user. Delegations are runtime overlays: they affect Roster resolution without rewriting provider-synced directory records.
Scopes
Section titled “Scopes”| Scope | Behavior |
|---|---|
all_participants | Delegates all current participant memberships for the delegator. |
participant | Delegates one specific participant membership. |
Participant-scoped delegations require a participant_id.
Timing
Section titled “Timing”Delegations can be open-ended or constrained by starts_at and ends_at.
Runtime status can be:
activeupcomingexpiredrevoked
Authorization
Section titled “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.
Resolve Behavior
Section titled “Resolve Behavior”When a delegated participant is selected, resolved users can include delegated
members with provenance fields such as delegated, delegated_by_*, and
delegation_id.