It appears docusign remembers the adopted signature for a certain email, regardless of, if they are a user or docusign member. Is there any way to turn off that feature?
In other words, we want our users to never have an adopted signature on file. Is this possible?
Yes there is an option in Preferences -> Features -> Signature Adoption screen that controls whether users can adopt their signature or not, shown here:
However this feature might not be enabled by default in your demo account. If it's not, you'll have to contact your Account Manager who can then turn it on for you. It's possible they will have to enable two options for your account - first you'll need access to the Signature Adoption settings if you don't have it already, then there's an option called "Disable Style Signature" which you also need checked on your account.
If you do not have an account manager yet please respond to the one or two emails you would have automatically received after account creation. You can also reach out to
service#docusign.com
for support and any other help you may need with accounts.
Related
I have an ASP, vb.net, forms-based system. I want to allow people to use PDF documents created within that system to send them to DocuSign and out to others for signature. I have used the DocuSign SDK to build a system that works; however, I am concerned that I may not have the best setup for that.
The problem relates to the "open" nature of this system. Our users are allowed to see and modify all parts of the underlying system, including forms, coding, etc. As a result, a clientID and secret would be seeable to users. And that is concerning.
The system will need to be set to be easily used by our users. So, having users set up a developer account, setting up API settings, etc., will not be something we can reasonably expect.
It would be better if the system did all the interaction and they just had to log on to DocuSign to send the document out for signing. DocuSign has suggested becoming a partner in their referral system. I worry that will still require all the pieces (clientID and secret) that people will be able to see. But, I am not sure that is true.
Will being a partner mean we can avoid having those items saved in an open system where users can see them? Or does being a partner mean some of that is removed or not necessary?
Is there a better way of setting this up so that we can avoid all that mess?
There's no reason that all your customers wouldn't be able to use the same clientID (also know as Integration Key or IK) and secret key (clientSecret).
You will be the only one that can see/set them as the ISV. They will all use their own DocuSign accounts, using your IK. That is abosltuly fine and does not have any limitations.
We recommend ISVs use a single IK per app if it's the same code for the app even if they have multiple customers using the app.
I am using the sandbox account and trying to setup an eNotary Profile. Being that its a sandbox area, I would assume that I don't need a valid notary ID to create one.
Can someone help me setup a Notary Profile on my sandbox account?
QA Question Newly Added: Will ALL test users have to go through this same process? or is it just the main account needs it setup. Reason being, we have a client that will be using the system. For our teams, and their teams, we will need accounts to test this.
Added Image
I assume you are talking about IDV which is a special kind of recipient authentication that require them to use an ID before they can sign a document.
This feature is not available in the sandbox normally because there's cost associated with each transaction.
We may be able to assist you on a case-by-case basis if you have a legitimate need to test this functionality in the developer sandbox.
see https://developers.docusign.com/esign-rest-api/guides/concepts/recipient-authentication for more information about recipient authentication.
Setting up eNotary requires some back-end switches to be flipped on your account. Please open a Support Case requesting that be enabled and provide your Demo account ID.
I want to release my application in play store and app store.
But, That store require PrivacyPolicyUrI But I don't use signup system
And most application has terms of policy in their signup view
it is essential?
So...
PrivacyPolicy is required for non-signup application, too?
Terms of policy is required even if I'm just developer not company?
Yes, a Privacy Policy is required even for apps that do not require sign-up. However, a sign-up screen is good as you can use the clickwrap method of getting active constent from users to accept your Privacy Policy.
The requirement of a Privacy Policy is due to sensitive permissions you app may ask.
You can find the list of those permissions here: https://play.google.com/about/privacy-security/personal-sensitive/
Even if you don’t need and ask those permissions, make sure you know what third parties you use in the app that might trigger this requirement (eg. AdMob).
You’ll need to add the URL to the Privacy Policy URL at Store Listing section. The link must be publicly accessible. Google will not host it for you.
A Terms of Service is not required, but it’s useful to add rules regarding user-generated content, unacceptable behaviour and so on. For example, it’s useful to add intellectual property clauses, ownership over your content and licenses over user-generated content clauses.
I am a developer using the Docusign API. When my users are tagging signature spots for their signers, I have disabled as many "tag types" as I can except for just SIGNATURE, INITIAL, FIRST/LAST NAME. However the users appear to have this "Formula" tag they can add which is of no use to us. I don't want it because it can confuse our users, but when I log into my account under Preferences/Features the "Enable Calculated Fields" checkbox is checked but greyed out so i cannot uncheck it.
I've looked at the Documentation and haven't figured out why this would be greyed out. There is no mention of this feature being tied to another feature. Is there any way to the formula/calculated-field tags?
Please ask either DocuSign Customer Service or your Account Manager for help to get this resolved. This is an account setting issue that probably needs to be updated on the platform for your account.
I am working on SOAP UI to test Docusign methods. I am getting emails and attachement with signature(anchor tab). But I am getting only signatures to be selected but not able to
allow user to sign using mouse. How to enable this feature?
Thanks.
I believe what you're talking about is how DocuSign gives signers the ability to adopt one of the default signature styles or you can draw your signature using the mouse. This is an account level setting that needs to be enabled in your account.
When your signers are signing if they do not have the ability to draw in their signature using the mouse, then most likely they have "Disable Draw Signature" checked in your account settings.
To resolve try the following:
1. Login to the Console.
2. Go to Preferences -> Features page.
3. There should be a "Signature Adoption Configuration" hyperlink. (if not contact your Account Manager to have that enabled)
4. Open the Signature Adoption Config screen by clicking the link.
5. Un-check the "Disable Draw Signature" option.
Then send another signature request and your recipients should have the ability to adopt their signature or draw their own.