Settings → Auto Delegation¶
Automatically route your signing turns to a backup person for a specific date range (e.g. while you're on vacation).
Endpoint summary¶
| Method | Path | Notes |
|---|---|---|
| GET | /user/v1/settings/auto-delegation |
View current settings |
| PUT | /user/v1/settings/auto-delegation |
Update |
| POST | /workflow/v1/auto-delegation/recipient-conflicts |
Check for conflicts before enabling |
Viewing and updating¶
{
"autoDelegationEnabled": true,
"autoDelegateEmail": "backup@example.com",
"autoDelegateName": "Sam",
"autoDelegationStartAt": "2026-08-10T00:00:00Z",
"autoDelegationEndAt": "2026-08-17T00:00:00Z",
"autoDelegationActive": false
}
autoDelegationActive is computed server-side (whether right now falls within the window) — it's not something you set directly.
PUT /user/v1/settings/auto-delegation
Content-Type: application/json
{
"autoDelegationEnabled": true,
"autoDelegateEmail": "backup@example.com",
"autoDelegateName": "Sam",
"autoDelegationStartAt": "2026-08-10T00:00:00Z",
"autoDelegationEndAt": "2026-08-17T00:00:00Z"
}
Checking for conflicts first¶
Before enabling, check whether the proposed delegate would create a routing conflict:
POST /workflow/v1/auto-delegation/recipient-conflicts
Content-Type: application/json
{ "emails": ["backup@example.com"] }
Flags cases like the proposed delegate already being a recipient on a workflow you're on, or the same delegate being shared across conflicting chains.
Once enabled, the platform can silently substitute your delegate at the moment your turn on any workflow starts — see Sending & Signing.