A classic. It was dramatized by the Rochester NY, USA Museum of Science as a planetarium show, and I saw it there about 1974 with my father. Great times.
Excellent. Remember, customers don't care about your app, per se. They don't want to become an expert user of your app. Customers care about getting their own work done and they hope that your app will assist them to do so. They want the hole, not the drill.
I am DocuSign’s Lead Developer Evangelist.
Thanks to Joseph (OP) for writing this up and to everyone who has contributed to this thread including both the positive and negative comments about integrating with DocuSign.
The problem OP ran into is really one of documentation and not a bug or security issue.
I agree that our docs for the embedded sender view should clearly state that the method’s URL gives full access to the sender’s account, and we’ll fix that ASAP. As others have commented, the assumption of this API method is that each sender has their own account. I also agree that the OP’s use case, which requires that the sender view’s capabilities be strictly limited to the current envelope, is valid. It is under consideration for our roadmap.
A workaround: I recommend that API applications complete the sending process programmatically including document tagging, etc. This also provides the best user experience for the sender.
We actively monitor and reply to the “docusignapi” tag on StackOverflow (I’m “Larry K”), if you want to reach out to us there.