Docusign integration

FileBound has teamed up with Docusign to offer a comprehensive document signature tool. The integration with Docusign allows documents to be sent for legally-binding e-signatures, right from the FileBound interface. Once a document is signed, it can be imported back into FileBound. For example, a FileBound user can send out contracts, loan agreement documents, employee forms, and other documents that require signature.

Note: The DocuSign integration is compatible with FileBound version 8.2.1.2 or later.

Note: This feature is only available for certain FileBound licenses. See FileBound licensing for more information.

Customers will need a Docusign Business-level or higher account for production.

Docusign offers an automatic import service called Docusign Connect. To use this capability, the customer’s FileBound site must be public-facing and use SSL.

Topics include: 

Obtain a free Docusign demo account

Step 1: Create an organization in Docusign

Step 2: Claim your domain in Docusign

Step 3: Configure Designated Senders in Docusign

Step 4: Configure Docusign in FileBound

Step 5: Configure Docusign Connect

 

Obtain a free Docusign demo account

FileBound partnered with Docusign to grant you access to a free Docusign demo account. Obtaining your free Docusign demo license is quick and easy.

  1. Navigate to https://developers.Docusign.com.

  2. Click Developer Account, then click Create account.

  3. Enter your information, then click Get Started.

Back to top

Step 1: Create an organization in Docusign

A Docusign organization is required for SSO and allows an organization to manage multiple Docusign accounts, users, and domains in a centralized location.

  1. Sign in to Docusign with Administrator credentials:

  2. Follow the detailed instructions on the Docusign support site to create an organization.

  3. Follow the detailed instructions on the Docusign support site to add users to an organization.

Step 2: Claim your domain in Docusign

Claiming an email domain in Docusign proves that you own the domain that users log in to Docusign with. Users added to an organization need to have the same domain as the domain that is claimed. A domain can only be claimed by one organization.

  1. Sign in to Docusign with Administrator credentials:

  2. Follow the detailed instructions in Docusign support to claim a domain.

    Note: You will need to work with your organization's IT administrator to edit your DNS settings.

Back to top

Step 3: Configure Designated Senders in Docusign

To use Docusign in FileBound, you will need to designate users in the Docusign system to send documents for signatures. These Docusign users need to be associated with a user in the FileBound system and given appropriate permissions in Docusign. These are Designated Senders.

Note: Full configuration of Docusign users is beyond the scope of the FileBound help center. See Docusign support for options and requirements not specified here.

  1. Sign in to Docusign with Administrator credentials:

  2. Under Users and Groups, click Permission Profiles.

  3. In the Actions drop-down, select Edit.

    Note: Docusign’s default permission profiles may not be editable. In this case, you will need to copy those to a new profile and edit that new profile instead.

  4. Click the User Permissions tab.

  5. Select the Allow view and manage envelope rights through API check box. All Designated Senders must have this permission applied.

  6. Select the Allow send on behalf of other users through API check box to allow the user to send envelopes on behalf of other users through the DocuSign API. See Docusign support for more information about this option.

  7. Click Save.

Step 4: Configure Docusign in FileBound

Once your Docusign account has been set up, configured, and the users have been added, the account can be easily integrated with FileBound.

Note: On September 30, 2024, Docusign is sunsetting basic authentication. If you use Docusign, you will need to reconfigure your Docusign integration to use OAuth 2.0 authentication prior to this. After this date, the "Docusign" integration for basic authentication will be removed from the UI and will no longer be accessible.

Tip: If you are an on-premise customer migrating from basic authentication to OAuth 2.0 authentication, or implementing a Docusign integration for the first time, you will need to contact your Customer Success Manager or Partner Success Manager with your URL in order for the integration to work properly. Your URL can be found in the address bar after logging in to your site (the "http://" or "https://" portion must be included).

  1. On the Navigation menu, click Administration, then click Main Options.

  2. Click Integrations.

  3. Select the DocusignOAuth integration, then click Edit.

    Note: By default, a DocusignOAuth integration is available. You cannot add a new DocusignOAuth integration or delete the existing DocusignOAuth integration.

  4. In the Docusign OAuth Settings window, configure the Docusign OAuth integration, then click Save.

Docusign Account Information

Enable Docusign Integration: Enables the Docusign integration.

Connect to demo Docusign account: Connects to a demo Docusign account.

Note: Changing from a production Docusign account to a demo Docusign account or vice versa will clear information regarding the Docusign account credentials and the designated senders.

  1. Sign in to Docusign with Administrator credentials:

  2. Click Organization in the Navigation menu.

  3. Click Users.

  4. Click View User next to a user in the organization with Docusign Admin permissions and copy the User ID. Paste this value in the DocuSign Admin User ID box, then click Verify to navigate to the Docusign log in screen.

  5. Enter the email address associated with your Docusign account, then click Next.

    Note: The user you sign in with must match the user whose user ID you entered in Step 1.

  6. Enter the password associated with your Docusign account, then click Next.

  7. Click Skip for Now and Log in.

    The credentials are verified. If the verification fails, you need to provide correct credentials.

  8. Click Save.

  9. Log out of FileBound and log back in to refresh your account settings.

  10. Return to editing the DocuSignOAuth integration.

  11. If you see An API Key Is Not Verified!, something went wrong. Go back to Step 1 and do not proceed until you see Verified.

Docusign Integration Options

Replace original document with signed document: Automatically replaces the original document in FileBound with any document imported from Docusign. If this option is not selected, a new document will be created in FileBound.

A document is replaced with the signed document only when all the users required to sign the document have signed it. The signed document will be in PDF format regardless of format of the original document.

Enable Docusign Connect: Automatically imports a document back into FileBound once it has been signed by all recipients. If this option is not selected, users need to manually import the signed documents from a viewer.

Docusign User: A user Docusign Connect will use to upload a document.

Designated Senders

You need to specify which FileBound user(s) will be able to send a document for signature. When adding a designated user, you need to map them to a Docusign account. A Docusign account can be mapped with one FileBound user only.

  1. Click Add.

  2. In the Docusign Designated Sender dialog box, select a FileBound user from the User list.

  3. Select an option from the Docusign Email list, to specify the Docusign account your want to map with the FileBound user.

    Note: Each Designated Sender must be configured in Docusign in order for this drop-down list to populate with user emails from your Docusign account. See Step 3: Configure Designated Senders in Docusign for more information.

  4. Click Save.

See Signatures for more information about sending documents for signature in Docusign.

Projects enabled for Docusign

You can enable the Docusign feature for specific projects or all projects. Select an option from the Select the projects that will be enabled for Docusign list. The following options are available:

  • None: Select this option if you do not want to enable the Docusign feature for any project.
  • All Projects: This option will enable the Docusign feature for all projects.
  • Selected Projects: This option allows you to enable the Docusign feature for selected projects. You need to select check box next to a project to enable the Docusign feature for that project.

Note: A project can be enabled for either Docusign or HelloSign. It cannot be enabled for both integrations.

Back to top

Step 5: Configure Docusign Connect

Docusign Connect is a service provided by Docusign, utilized by the FileBound integration to push documents back into FileBound automatically once they have been signed by all recipients.

Note: The FileBound site needs to be public‐facing and use SSL to use the Docusign Connect service.

Note: This service will only be available if it has been configured in Docusign AND 'Enable Docusign Connect' has been selected by a System Administrator in the Docusign Integration settings for your site.

  1. Sign in to Docusign with Administrator credentials:

  2. Under the Integrations section in the Navigation Menu, click Connect.

  3. Click Add Configuration, then click Custom.

  1. Type a name for the Connect configuration in the Name field.
  2. Type [your FileBound site URL]/process/Docusignconnect.ashx in the URL to Publish (HTTPS required) field. 
  3. Select the Enable Log (maximum 100) check box.

  4. In the Event Settings section, under Trigger Events, click Envelope and Recipients to expand the section.
  5. Select the Envelope Signed/Completed check box.

    Note: The remaining envelope and recipient events are not currently supported.

  6. Click Include Data to expand the section.

  7. In the Associated Users/Groups section, determine which of your Docusign users you want to enable the Docusign Connect feature for.
  8. Click Add Configuration.

Back to top