Skip to main content

Hello DocuSign Community,

We’re integrating DocuSign with our internal system via the REST API and encountered an issue with controlling permissions in Sender View.

What works:

  • We successfully create an envelope via API with attached documents.

  • The envelope remains in created status, as intended.

  • We then create a Sender View (embedded) using the CreateSenderView API call.

Our goal:

We want the sender to add tabs (fields) for other recipients, but not be able to:

  • Edit or remove the document itself

  • Add/remove recipients

  • Change routing or envelope metadata

What we tried:

We passed the following parameters into the ReturnUrlRequest (as described in the documentation):

{  "returnUrl": "https://ourapp.com/return",  "configuration": {    "disableDocumentEdit": "true",    "allowRecipientRecursion": "false",    "allowComments": "false",    "allowReassign": "false",    "messageLock": "true",    "useDisclosure": "false"  }}

Problem:

Despite passing all the configuration flags, the resulting Sender View still shows all buttons and options, including:

  • "Edit Document"

  • "Add/Remove Recipients"

  • And the sender can actually perform those actions.

It appears that the configuration is not being respected, or that we're missing something crucial.

Questions:

  1. Are these config options still supported in current API versions?

  2. Is there any other way to allow only field placement while locking all other editing options in Sender View?

  3. Should we use a specific user role (like Editor) instead?

  4. Could this behavior depend on account-level permissions?

Thanks in advance for your support!
We would greatly appreciate an example or working configuration that enforces field-only editing.

 

Hi ​@Alina.Der 
 

Editing document and recipients is done at the “Prepare” page. You can achieve the task by bypassing the “Prepare” page and opening directly the “Tagger” page by setting the “startingScreen” to “Tagger”. 

Disabling the back button will prevent the sender to go back to the “Prepare” page.

It seems your JSON body is incorrect because the CreateSenderView request object does not contain “configuration” 

We have free online tool you can play with different options and see how the singing experience will look like 
 

I hope this helps


Hi @Ivan.Dinkov 

Thank you so much for your detailed and clear response — it solved our issue perfectly!

The demo tool you linked is a fantastic resource — it helped us test things out quickly and confidently.

Really appreciate your support and guidance!
Wishing you a great day ahead 😊


Reply