DocuSign "ACCOUNT_LACKS_PERMISSIONS" on bulk send

Fix DocuSign "ACCOUNTLACKSPERMISSIONS" on bulk send

TL;DR

Confirm the plan includes Bulk Send and the sending user has the permission enabled. Single envelopes can work fine while bulk send is rejected, because bulk is a separately entitled feature with its own per-user switch. Enable both and retry.

{
  "errorCode": "ACCOUNT_LACKS_PERMISSIONS",
  "message": "This Account lacks sufficient permissions to perform Bulk Send."
}

1. Check the account plan includes Bulk Send. It is not on every plan. Expected: you confirm the entitlement or find it missing.

2. In the Admin console, grant the sending user the Bulk Send permission. Expected: the permission shows enabled for that user.

3. Retry the bulk send request unchanged. Expected: the bulk list is accepted.

Use this when

• single envelopes send fine but bulk send is rejected
• the error names account permissions on a bulk operation
• a new user cannot bulk send while colleagues can

Not for this skill when

• all sending fails, not just bulk (an account or credential problem)
• the bulk list itself has errors (fix the recipient data)
• you need bulk send on a plan that does not include it (talk to sales or change plans)

Variant phrasings

• docusign ACCOUNTLACKSPERMISSIONS bulk send
• docusign bulk send permission denied account plan
• docusign enable bulk send for user admin
• docusign bulk send entitlement missing

Why it happens

DocuSign gates Bulk Send twice: the account plan must entitle it, and each sending user needs the permission switched on. Either gate closed produces the same error, and single-envelope sending passing makes the bulk-only failure confusing.

Edge cases

• Permission changes can take a few minutes to propagate; retry after a short wait.
• Bulk send has its own rate limits separate from normal sending; plan large batches accordingly.
• The permission is per user, not per integration key; each service user needs it.
• Test with a two-recipient bulk list before launching the full batch.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_A5wXsVYNY2LVdBRVxUQGtA