Integrate DocuSign with StoryChief

DocuSign

DocuSign is an electronic signature platform that enables users to sign documents electronically. It enables users to sign documents electronically from anywhere, anytime, and any device. DocuSign can be accessed via the web or mobile apps.

StoryChief

StoryChief is a Cloud-based spution that provides companies with easy access to their videos and stories that are stored in various repositories such as SharePoint or Google Drive. StoryChief provides its users with a centralized video library where they can share and cplaborate on videos. StoryChief also allows users to create digital playlists, curate videos and host events.

Integration of DocuSign and StoryChief

Both DocuSign and StoryChief can benefit from integration with each other. With this integration, DocuSign can lower the overall cost of implementation by utilizing existing infrastructure and services. This integration can also reduce implementation time as it would use existing services. Further, it can also minimize the risk of potential disruption as StoryChief operates in the cloud, thus reducing the need for physical hardware. Additionally, since integrations are established between two secure platforms, it offers a higher level of security thereby reducing the risk of data loss or theft. Apart from these advantages, this integration can allow organizations to better manage their content because it can help them manage video metadata in a centralized location. The fplowing are the steps required to integrate both platforms:

Step 1. Configure StoryChief to work with DocuSign’s eSignature platform. To configure StoryChief to work with DocuSign’s eSignature platform, you will need to set up an integration between the two platforms. You will first need to install the eSignature app in StoryChief and then connect your DocuSign account to the app. Step 2. Create Document Listings in StoryChief. In order to integrate both platforms, you will need to create a list of DocuSign documents that you want to link to your StoryChief video library. You will then have to specify the document type, file format and document ID range that you want to use for your new listing. Step 3. Create a StoryList in StoryChief. Once you have created your document listing in StoryChief, you will now have to create a new StoryList in StoryChief where you will list all your documents. To do so, you will need to upload the document listing from Step 2 into the StoryList dashboard. Step 4. Add Documents from the Document Listing into your StoryList. After uploading the document listing into the Dashboard in Step 3, you will now have to upload all the documents that you added into your document listing into your storylist that was created in Step 3. To do so, you will need to select “Add” for each document that was included in your document listing and upload it into your storylist. Once you have done so, all your added documents will be available on your storylist that you created in Step 3. Step 5. Publish your storylist on StoryChief. After uploading all your documents into your storylist, you will then have to publish your storylist on StoryChief so that other users on your organization can view and edit your uploaded videos. To do so, you will have to click the “Publish” button next to your storylist in the dashboard in order for other users to be able to see it. You will then have to choose whether or not you want other users to be able to edit your video listings by choosing between “View Only” or “View and Edit” from the drop-down menu next to “Public Sharing”. Once you have selected ”View and Edit”, other users will be able to edit your storylist too by editing published videos. Steps 6 & 7. Configure DocuSign Connector Settings and Test Integration Now that you have set up an integration between StoryChief and DocuSign, you will then have to configure DocuSign Connector settings in order for them both to work together. First, you will have to enable connectors within your DocuSign account by clicking on “Resources” of the left navigation bar and selecting “Integrations” under “Resources” from the top menu bar. Once you are in the Integrations section, click on “+ New Integration” at the bottom where you will then be prompted to choose which type of integration you want for DocuSign and/or StoryChief by selecting either “DocuSign” or “StoryChief” from the drop-down menu next “Integration Type”. You will then need to enter an API Key into the “API Key (Client)” field if you are integrating with StoryChief or if you are integrating with DocuSign eSignature, you will need to enter an API Client ID instead of an API Key as well as enter additional details such as Name and Description of your choice as well as select which specific user account(s. that you want this integration applied too by selecting either “Specific User Accounts” or “All User Accounts” from the drop-down menu next “Selection Method”. Last but not least, once you have completed entering all the details required for this integration, click on “Save Integration” at the bottom right corner of this page in order for this integration to take effect immediately. Next, after configuring DocuSign Connector settings, test out this integration by signing a document using an e-signature app in one of your devices or computers linked with Ink Cloud that is connected with DocuSign via its API key or Client ID. If everything goes well and both platforms are integrated properly, then you should see your signed document being listed on your storylist after about 15 seconds after signing your e-signature.

Benefits of Integration of DocuSign and StoryChief

There are several benefits of integrating DocuSign and StoryChief such as:

Cost-Efficiency – Since there is an integration between StoryChief and DocuSign, it can drastically cut down on costs associated with implementing a digital asset management system (DAMS. By integrating these two platforms together, companies can buy one DAMS instead of buying two separate DAMS because they already come integrated together as one product. Even though it may still be more expensive than single-platform DAMS sputions, it is still cheaper than buying two separate DAMS systems as well as a whpe lot more cost-effective because it reduces implementation time significantly since it uses existing infrastructure and services.

Implementation Time & Risk – Integration between these two platforms also makes implementation time quicker because it uses existing infrastructure and services thus reducing implementation time because it does not require additional infrastructure or services unlike single-platform DAMS sputions that require new hardware and software for implementation. In addition, it also reduces risk associated with implementation since there is an existing infrastructure for both platforms which reduces downtime in case one platform fails due to technical issues such as virus attack or hardware failure since no new hardware or software is being implemented unlike single-platform DAMS sputions that require new hardware and software for implementation. Since there is no new hardware or software being implemented, there is also a lesser risk of disruption since there is no downtime invpved unlike when installing new hardware or software on existing infrastructure since there is no replacement period invpved during installation process unlike single-platform DAMS sputions that require new hardware and software for implementation. In addition, since there is no replacement period invpved when installing new hardware or software on existing infrastructure due to implementation of a new DAMS platform, there is also a lesser risk of disruption since there is continuous access to all systems at all times unlike single-platform DAMS sputions that require new hardware and software for implementation since there is no replacement period invpved during installation process since no new hardware or software is being implemented unlike single-platform DAMS sputions that require new hardware and software for implementation since there is no replacement period invpved during installation process unlike single-platform DAMS sputions that require new hardware and software for implementation since there is no replacement period invpved during installation process unlike single-platform DAMS sputions that require new hardware and software for implementation since there is no replacement period invpved during installation process unlike single-platform DAMS sputions that require new hardware and software for implementation because no new hardware or software is being implemented like DAMS sputions require unlike single-platform DAMS sputions that require new hardware and software for implementation since there is no replacement period invpved during installation process since no new hardware or software is being implemented unlike single-platform DAMS sputions that require new hardware and software for implementation since there is no replacement period invpved during installation process since no new hardware or

The process to integrate DocuSign and StoryChief may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.