HelloSign integration

FileBound has teamed up with HelloSign to offer a comprehensive document signature tool. The integration with HelloSign 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: This feature is only available for certain FileBound licenses. See FileBound licensing for more information.

Configure HelloSign in FileBound

Once your HelloSign account has been set up and users have been added to a team, the account can be easily integrated with FileBound.

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

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

  3. Select the HelloSign integration, then click Edit.

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

HelloSign Account Information

Enable HelloSign Integration: Enables the HelloSign integration.

Connect to HelloSign Account in Test Mode:Test mode can be used to see how the integration will work prior to use. Documents are sent through the test HelloSign system and signatures are not legal.

HelloSign API Key: The API Key of the HelloSign account used to send signature requests. See the HelloSign documentation for more information about finding your API key. After entering your API key, click Verify to ensure that it is correct.

HelloSign Integration Options

Replace original document with signed document: Automatically replaces the original document in FileBound with any document imported from HelloSign. 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.

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 HelloSign account.

  1. Click Add.
  2. In the HelloSign Designated Sender dialog box, select a FileBound user from the User list.

  3. Click Save.

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

Projects enabled for HelloSign

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

  • None: HelloSign will not be enabled for any projects.
  • All Projects: HelloSign will be enabled for all projects.
  • Selected Projects: Select the Enabled check box next to each project you want the HelloSign integration to be enabled for.

API Key: The API Key of the HelloSign account used to send signature requests. Projects enabled to HelloSign will use the default key above if no key is specified.

Client ID: The Client ID from the HelloSign API settings. Client ID can be used to customize some of the signature requests, such as the company logo, when sending signature requests from the same API Account. This field is optional.

Test Mode: Test mode can be used to see how the integration will work prior to use. Documents are sent through the test HelloSign system and signatures are not legal.

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