Short version: Does the DocuSign API have the ability to send different templates from different user accounts?
Long version: We have a web form that gathers information - chooses the template id and pre-fills info into a form and then sends it along to signers. Right now our programmer coded a procedure that sends all templates out of one user account so all docs are listed in one account. We want to change that so different templates originate from different user accounts which can be easily determined at the template creation point.
Is this possible? If so, what is the API call or specs to make this happen? Is there anything on the account side that needs to change?
Yes there's a solution for this, but first let me clarify. You can only send from a template that's in your account.. you can not access templates from other accounts.
With that said, all of you have to do is copy or migrate the templates into the account that you want to send from. There's two general methods of doing this:
Manually download the templates from the first account then re-upload into the second account using the DocuSign website.
Programmatically download the templates from account A then create (or POST) the templates up into the second account.
Obviously you'll need valid user credentials from each account to be able to access the templates and upload, and I believe only users with Admin privileges can do this.
For #1 here's a guide that explains how to download/upload templates through the DocuSign UI: https://support.docusign.com/en/guides/ndse-user-guide-download-template
For #2 see the Templates: get call to retrieve a single template, see Templates: list to list all account templates, and see Templates: create to upload (or create) a new one in a given account.
Related
Is it easy for people to find "public" google sheets/docs?
Context: Storing some semi-sensitive data (individual user info, of non-sensitive nature) for an app beta-test in google sheets. Planning to migrate to some DB in the future, but for now, just using JavaScript to pull the data directly from the google sheets (since there are visualizations being dynamically updated by the sheets).
Yes, it's easy to get information. Search engines may index and cache the information. Then, there are bots, crawlers and scrapers. Do NOT put (semi)sensitive information in public. Implement google-oauth properly with google-sheets-api to get information. You can also use service-accounts
Yes, it can be easily accessed.
According to the official Google article Share files from Google Drive: when you set your file's General Access setting to public:
Anyone can search on Google and get access to your file, without signing in to their Google account.
What you can do:
In the case of your app beta-test in google sheets data, you may want to reconsider to change your file's General Access setting to one of the following (in descending order of security):
Restricted - Only people that you manually give access to can view or edit your files. When you click the share button, a prompt will show and you may manually add the users who can view or edit your files:
Afterwards, you may select a role for those users and then they can be notified afterwards through email.
On the other hand, you can share the link to others. A prompt will show like the one below if you send the url through Google Chat:
You may opt to select Don't give access which will result in the following view on the other user's end:
This would mean that if unauthorized users get hold of the file URL, they will still need to send an access request. If other users submit the request, an email notification will be sent to your mail inbox. Other users who also own the file will also be notified by mail.
Your Organization - If you use a Google Account through work or school, anyone signed in to an account in your organization can open the file. If you are an administrator in a work or school workspace, you may set how members can share content within the organization. The administrator can prevent the sharing of content with group members outside your organization. If external sharing is prohibited, only group members who are in your organization can access the group's shared content.
Anyone with the link - Anyone who has the link can use your file, without signing in to their Google Account. This option is least recommended because if the URL is leaked to unauthorized users, they can easily access the file.
References:
Share files from Google Drive
Share content with a group
Don’t make it public unless you want the public to see it. Use oauth to access.
We have a developer account and I am starting to integrate it into our system. The system is based on Laravel/VueJS and I've 2 additions Eric Tucker Docusign SDK and the official Docusign SDK.
I've managed to create a template in our developer area, with custom fields (a question later regarding them) but wonder what happens when I have completed the system on our website. What happens going live? I presume that any template created in our account is used by associated users on our system - or do they have to create templates on their account and create custom fields etc?
When you go live you'll have to move your templates/custom fields to the new production account (or the existing one).
More information about going live - https://developers.docusign.com/platform/go-live/
I have some doubts regarding the custom connector we are trying to build for docusign : -
Regarding the license plan that need to be bought by the customers who will be granting access for our connector to collect data from their docusign organization account. I am looking at the link https://www.docusign.com/products-and-pricing. API access support is mentioned in only the advanced solution. So I was wondering whether only we need to have "Advanced solutions plan with APIs support" plan or all our customers need to API access support in order to fetch their data.
As per the documentation, to make the REST API calls we need two fields 'base_uri' and 'account_id' (https://developers.docusign.com/esign-rest-api/guides/authentication/user-info-endpoints). Now, the response of userInfo API call gives an array of accounts and its respective fields. My doubt is, if multiple authenticated users (more than one accounts) are returned in this array but all are part of same organization, will they all have different account_ids. Main concern here is, will there be several Base Paths (https://developers.docusign.com/esign-rest-api/guides/authentication/user-info-endpoints#form-your-base-path) to make API calls?
2a. Further question is, what is the significance of 'is_default' field?
Is this related to main account (if is_default is true) using which we will create our Base Path?
Since this is a tech/engineering forum I'm going to answer only question #2 as question #1 is more of a business/sales question.
The reason you may get multiple accounts is that an authenticated user in DocuSign can be a member of multiple accounts. That said, it's the same user. Meaning, say foobar#blah.com has an account 123 with company X and account 456 with his school, then it's possible that when foobar#blah.com authenticates (With the same password!) to DocuSign we have a list of accounts associated with that user. We give you all of them when you make the API call. The default one is the main one that you would see when you log into our web app. You can decide yourself as the user which one is the default. Users who log into our web-app then see an option at the top-right to change accounts.
and yes, every API call is associated with a specific account. So when you construct the urls for your API - you do need to know which account for this user you are making the API call for. Your application can decide how to handle this.
Hope this helps.
It appears that it is possible to generate an envelope using a template that does not belong to the account that was authenticated in the REST call. The two accounts were completely unrelated. Access to the generated envelope is limited to the account that generated the envelope; however the access to the template seems to be allowed to any account.
Scenario where this behavior was noticed:
- Account 1 - Created Template #1
- Account 2 - Generate an envelope using Template ID generated by Account 1
I could not find documentation or configuration related to behavior.
I need to confirm if the behavior is intended/supported before we plan to utilize the functionality.
Probably your best solution if you want to use Templates from one account in another is to simply move them. You might only be able to do this in the classic UI so you might have to switch back through your preferences, but you can:
Download the actual XML for each template you want to "share" across accounts.
Open the second account and select to upload template(s) and chose the XML files you downloaded.
As mentioned you might have to switch back to the classic UI to download/upload, but you definitely will not be able to use Templates from one account when you are an un-authenticated user in another account.
I am writing an application that uses Docusign and I’m trying to figure out the best way to manage my Docusign account in general.
Here is the use case:
1) My software uses custom Docusign templates and tabs and uses the Docusign API to accomplish populating the templates, tabs, and generating envelopes
2) The user will have to provide their own Docusign account to use my software
Questions:
1) How do I get the custom templates loaded into their Docusign account?
Can templates be shared between totally disparate Docusign accounts?
Other options I think might work are an export or import of the templates (but that is clunky).
Maybe I can use the API to upload the templates as well???
2) Who’s Docusign Integrator Key do I use?
Do they need to generate one from their Docusign account and I use that one from my software? Or do I ALWAYS use my developer integrator key???
3) Who’s API username and password do I use to log in via the API?
I assume theirs, but I’m not a fan of needing to save a bunch of Docusign passwords in my database.
Any other options for setting this up the right way???
Thanks everyone!
For future inquires, include if you're using REST or SOAP.
Here are the answers to the questions that you have above.
1) How do I get the custom templates loaded into their Docusign account?
Can templates be shared between totally disparate Docusign accounts?
Other options I think might work are an export or import of the templates (but that is clunky).
Maybe I can use the API to upload the templates as well???
Templates can only be shared within users on the same account. There isn't a way to upload a template via the API either. You can use composite templates for a standardized template across multiple accounts (depending on SOAP/REST, the coding changes here)
2) Who’s Docusign Integrator Key do I use?
Do they need to generate one from their Docusign account and I use that one from my software? Or do I ALWAYS use my developer integrator key???
Your application will always use your Integrator Key, which will only work in Demo until you go through the Certification to get the Integrator Key promoted to production.
More info on that process here: https://www.docusign.com/developer-center/go-live/certification
3) Who’s API username and password do I use to log in via the API?
I assume theirs, but I’m not a fan of needing to save a bunch of Docusign passwords in my database.
Any other options for setting this up the right way???
You will need specific permissions enabled on a user and on an account to make API calls successfully. Most integration's use a system user to login and make these calls. If you're working within multiple accounts that you do not have administration over, you will end up running into permission errors.
It sounds like you're wanting to setup a Partner integration, which does differ a little from a standard integration.