Skip to main content
Question

Getting ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE when using embedded signing with a different user

  • May 20, 2026
  • 1 reply
  • 60 views

Forum|alt.badge.img+1

Hello,

I am experiencing an issue with the embedded signing flow and would appreciate any guidance.

Scenario:
We create envelopes using a system administrator account via the eSignature REST API, then attempt to generate an embedded signing URL (CreateRecipientView) while authenticated as a different DocuSign user.

Error received when calling CreateRecipientView:

{
"errorCode": "ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE",
"message": "This account is not authorized to access the requested envelope."
}

What we have confirmed so far:

  • The envelope is successfully created by the admin account.
  • The accountId used in the CreateRecipientView endpoint matches the one used during envelope creation.
  • recipientId and clientUserId are set in the CreateEnvelope request.
  • The signer email/name matches the recipient definition.
  • We are using a different authenticated DocuSign user (different access token) when calling CreateRecipientView.

Questions:

  1. Does CreateRecipientView need to be called using the same DocuSign user (access token) that created or owns the envelope, even if the embedded signer is a different recipient?
  2. If another user within the same DocuSign account calls CreateRecipientView, are additional permissions or shared access settings required?
  3. Are there other common causes of ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE that we should check?

Any advice or documentation references would be greatly appreciated.

Thank you.

1 reply

Forum|alt.badge.img+5
  • Docusign Employee
  • May 21, 2026

Hi ​@Aung 


Thanks for reaching out to the Docusign Community.
 

The ACCOUNT_NOT_AUTHORIZED_FOR_ENVELOPE error usually means the API is trying to access an envelope created in a different DocuSign account, or the embedded signing user session doesn't match the envelope. The API credentials (Integration Key/Token/User) making the RecipientView request must belong to the exact same account that generated the envelope. I guess that's what went wrong in this case. The other reasons for this error are a missing clientUserId for that recipient or a mismatched environment (demo vs. prod).
 

Best regards,