# HelloSign for Salesforce Admin Guide Documentation

> Documentation for HelloSign for Salesforce Admin Guide

## Guides
- [Quick Start Guide](https://sfdc-docs.hellosign.com/docs/getting-started.md): Follow these quick and easy steps to get Dropbox Sign for Salesforce configured in no time at all. Dropbox Sign for Salesforce works with both Classic and Lightning Salesforce Experiences, all walkthroughs will be in Lightning.
- [Compatibility](https://sfdc-docs.hellosign.com/docs/compatibility.md): Dropbox Sign for Salesforce is built on Lightning. Our product is fully compatible to both Lightning and Classic.
- [Installing Dropbox Sign for Salesforce from the AppExchange](https://sfdc-docs.hellosign.com/docs/installing-hellosign-for-salesforce-from-the-appexchange.md): Installing the Dropbox Sign for Salesforce app into your production or sandbox is easy. Following these simple steps and get started now.
- [Creating a Dropbox Sign for Salesforce Free Trial](https://sfdc-docs.hellosign.com/docs/creating-a-hellosign-for-salesforce-free-trial-1.md)
- [Connecting Dropbox Sign to Salesforce](https://sfdc-docs.hellosign.com/docs/connect.md)
- [Add “Use Dropbox Sign” and Dropbox Sign Signature Request related list to a page layout](https://sfdc-docs.hellosign.com/docs/add-use-hellosign-and-hellosign-signature-request-related-list-to-a-page-layout.md): The following STEPS can be applied to any of the out-of-the-box supported objects (Opportunity, Account, Lead, Contact).  The same STEPS apply for standard and custom objects once configuration for those objects has been completed.
- [Add Dropbox Sign Lightning Components (optional)](https://sfdc-docs.hellosign.com/docs/add-hellosign-lightning-components.md): Dropbox Sign provides four Lightning components that can be added to any Dropbox Sign supported object. These components allow users with access to send a signature request as a one-time, or from a template. You can also add the Create Template option as well.
- [User Permissions to Send for Signature](https://sfdc-docs.hellosign.com/docs/user-permissions-to-send-for-signature.md): Dropbox Sign for Salesforce provides two permission sets that can be found in Setup > Manage Users > Permission Sets. They are titled “Dropbox Sign_User” and “Dropbox Sign_Admin”. These permission sets can be cloned to make custom versions to fit whatever use cases you may have.
- [Manage Template Access](https://sfdc-docs.hellosign.com/docs/manage-template-access.md): Controlling access to templates provides greater security and compliance. The following section outlines different methods for controlling access to Dropbox Sign Templates.
- [Default Templates](https://sfdc-docs.hellosign.com/docs/default-templates.md): Default templates are managed on the Supported Objects page within Dropbox Sign Settings. Default templates allow admins the ability to present users with the correct template based on information stored on the record. Dropbox Sign default templates leverage Salesforce formula and lookup fields making this feature incredibly flexible.
- [Example - Default w. Formula](https://sfdc-docs.hellosign.com/docs/example-default-w-formula.md): Dynamically determine which template to use via a formula field
- [Example - Default w. Lookup](https://sfdc-docs.hellosign.com/docs/example-default-w-lookup.md): Dynamically determine which template to use via a lookup field
- [Salesforce Sharing Settings](https://sfdc-docs.hellosign.com/docs/salesforce-sharing-settings.md): If there are templates that should only be accessed by certain groups of users Salesforce Sharing Settings allow you to limit template access. The following steps outline an example of how to restrict access.
- [Additional Configuration Settings](https://sfdc-docs.hellosign.com/docs/additional-configuration-settings.md): Once you’ve completed the Quick Start Guide you are ready to start using Dropbox Sign for Salesforce with one-time documents. In the following sections we will cover additional configuration settings and functionality included in Dropbox Sign for Salesforce.
- [Manage Team or Billing Settings on hellosign.com](https://sfdc-docs.hellosign.com/docs/manage-team-or-billing-settings-on-hellosigncom.md)
- [Route Signers to URL](https://sfdc-docs.hellosign.com/docs/route-signers-to-url.md): Once a signer has completed a request they will be directed to the url stored in this setting.
- [Signed Document Routing](https://sfdc-docs.hellosign.com/docs/signed-document-routing.md): All signed documents are saved within salesforce.com for future reference. Document Routing allows the admin to specify where all signed, completed documents are stored, either to Files (aka, Content Documents) on the source record or to Notes & Attachments (aka, Attachments).
- [Exclude Final Signed Documents](https://sfdc-docs.hellosign.com/docs/omit-final-signed-documents.md)
- [Scheduling Template Synchronizations](https://sfdc-docs.hellosign.com/docs/scheduling-template-synchronizations.md): To keep Dropbox Sign templates synchronized between hellosign.com and native Dropbox Sign Template records, a scheduler can be used to check between the different repositories to ensure they are aligned. This can be scheduled every hour or every day, and can be run immediately, if desired. Organizations who do frequent template curation should schedule it every hour.
- [Disconnecting Dropbox Sign from Salesforce](https://sfdc-docs.hellosign.com/docs/disconnecting-hellosign-from-salesforce.md)
- [Format Date/Datetime Merge Fields by User Locale](https://sfdc-docs.hellosign.com/docs/format-datedatetime-merge-fields-by-user-locale.md)
- [Multi-Language Support](https://sfdc-docs.hellosign.com/docs/multi-language-support.md): Dropbox Sign for Salesforce supports 21 languages.
- [Salesforce Environment Management](https://sfdc-docs.hellosign.com/docs/salesforce-environment-management.md): Dropbox Sign for Salesforce supports multiple connections to Salesforce environments. Your Dropbox Sign connected user can be linked to multiple production or sandbox environments.
- [Use in Production and Test in Sandbox](https://sfdc-docs.hellosign.com/docs/use-in-production-and-test-in-sandbox.md): Dropbox Sign for Salesforce supports connections to multiple Salesforce environments.
- [Migrate from Sandbox to Production](https://sfdc-docs.hellosign.com/docs/migrate-from-sandbox-to-production.md): It is always best practice to test in a sandbox. This includes testing apps such as Dropbox Sign for Salesforce. Once you have properly tested and verified functionality is working correctly there are a few steps to migrate functionality from a sandbox to your production environment.
- [Connect to Multiple Production Environments](https://sfdc-docs.hellosign.com/docs/connect-to-multiple-production-environments.md): Dropbox Sign for Salesforce supports connections to multiple Salesforce environments.
- [Template Types](https://sfdc-docs.hellosign.com/docs/template-types.md): Dropbox Sign has a variety of template types that are outlined in this section.
- [Sign via email](https://sfdc-docs.hellosign.com/docs/via-email.md): Allow a Salesforce user to send a signature request via email from within Salesforce.
- [Sign in-person](https://sfdc-docs.hellosign.com/docs/sign-in-person.md): Allow a Salesforce user to initiate an in-person signature request in Salesforce.
- [User signs](https://sfdc-docs.hellosign.com/docs/user-signs.md): Allow the Salesforce running user to sign a document directly in Salesforce.
- [Creating a Template](https://sfdc-docs.hellosign.com/docs/creating-a-template.md): Dropbox Sign templates allow users to format a document once and then save the prepared document in Salesforce. When the template is opened for use, the previously saved formatting holds, and the signing flow can be initiated without having to drag and drop fields again. Templates are perfect for high volume documents like sales contracts, tax forms, investment agreements, HR paperwork, rental leases, and more.
- [Template Properties](https://sfdc-docs.hellosign.com/docs/template-name-source.md)
- [Template File Source](https://sfdc-docs.hellosign.com/docs/template-file-source.md)
- [Template Recipients](https://sfdc-docs.hellosign.com/docs/template-recipients.md): The recipients page contains two sections: Signer Options and Recipients. This page determines who needs to receive the document, the order delivered, and what options signers have.
- [Template Signer Attachments](https://sfdc-docs.hellosign.com/docs/template-signer-attachments.md): For each recipient on the Recipients page, you can choose to request files from signers when they sign the document.
- [Template Merge Fields](https://sfdc-docs.hellosign.com/docs/template-merge-fields.md): Templates can include Salesforce data. This data when selected will be mapped into your document either through the Dropbox Sign template editor or via text tags.
- [Template Writeback Fields](https://sfdc-docs.hellosign.com/docs/template-writeback-fields.md): Templates can include Salesforce data that is editable by the signer. Changes to writeback fields are updated in Salesforce.
- [Template Delivery](https://sfdc-docs.hellosign.com/docs/template-delivery.md): This page allows you to determine what message to send recipients and the methods in which users send the template.
- [Template Dropbox Sign Editor](https://sfdc-docs.hellosign.com/docs/template-hellosign-editor.md): If you are using the file upload method you will be taken to the Dropbox Sign editor to map your signature and merge fields (optional).
- [Template Draft or Publish](https://sfdc-docs.hellosign.com/docs/template-draft-or-publish.md): Templates can be saved either as a draft or as published. Draft templates are not available to users until they are marked published. Published templates will be made available immediately to users.
- [Editing a Template](https://sfdc-docs.hellosign.com/docs/editing-a-template.md): Templates can be saved as drafts or as published.
- [Archiving a Template](https://sfdc-docs.hellosign.com/docs/archiving-a-template.md): Archiving a Dropbox Sign Template in Salesforce will remove the template from the Use Template selection list. Archiving a template in Salesforce will not remove the template from Dropbox Sign. See additional steps for archiving templates associated with CPQ Quote Templates.
- [Unarchiving a Template](https://sfdc-docs.hellosign.com/docs/unarchiving-a-template.md)
- [Send with Template](https://sfdc-docs.hellosign.com/docs/send-w-template.md): Outlines all the behavior of sending with a template.
- [Invocable Send with Template](https://sfdc-docs.hellosign.com/docs/invocable-send-with-template.md)
- [Send One-Time Document](https://sfdc-docs.hellosign.com/docs/send-one-time-document.md): Dropbox Sign supports sending one-time documents. This allows users to select a document, define the recipients, and set the message. Merge fields are not available for one-time documents.
- [Open Signature Requests](https://sfdc-docs.hellosign.com/docs/open-signature-requests.md): There are a handful of actions users can take with open signature requests. This sections covers what those actions are and how to use them.
- [Default Automatic Reminders](https://sfdc-docs.hellosign.com/docs/default-automatic-reminders.md)
- [Signature Reminders](https://sfdc-docs.hellosign.com/docs/signature-reminders.md): A Signature Request can support multiple signers. For those taking their time to sign users can send a friendly reminder. In this section we cover how to send a reminder, disabling Dropbox Sign automatic reminders, and adding/removing reminders for users.
- [Invocable Reminder](https://sfdc-docs.hellosign.com/docs/automated-reminders.md): Reminders can be invoked via Salesforce Process and Flow Builder allowing you to incorporate signature request reminders into Salesforce workflows.
- [Cancel Signature](https://sfdc-docs.hellosign.com/docs/cancel-signature.md): Allow users to cancel an open signature request.
- [Invocable Cancel](https://sfdc-docs.hellosign.com/docs/invocable-cancel.md): Cancel can be invoked via Salesforce Process and Flow Builder allowing you to incorporate signature request cancelations into Salesforce workflows. See our Cancelation Example.
- [Reminder and Cancel Buttons](https://sfdc-docs.hellosign.com/docs/removing-reminders-or-cancel.md): Reminders and Cancel buttons can be added to or removed from any Signature Request page layouts you have in your org. Admins can add and remove the Reminder and Cancel buttons by following these steps:
- [Example: Set Custom Reminder then Cancel process when using a HelloSign Template](https://sfdc-docs.hellosign.com/docs/example-set-custom-reminder-then-cancel-process-when-using-a-hellosign-template.md): This example outlines how you can set scheduled reminders followed by the cancelation of a signature request when using a specific HelloSign Template.
- [Add Dropbox Sign on Standard and Custom Objects](https://sfdc-docs.hellosign.com/docs/hellosign-on-standard-and-custom-objects.md): HelloSign supports Accounts, Contacts, Leads, and Opportunities out-of-the-box.  Additional objects (both standard and custom) require a few additional steps to set up. Each of the steps is outlined in detail below.
- [1. Add lookup Field to Object from HelloSign Signature Request](https://sfdc-docs.hellosign.com/docs/1-add-lookup-field-to-object-from-hellosign-signature-request.md): The HelloSign Signature Request object stores signature data necessary for HelloSign to function. In order to use HelloSign on custom and non out-of-the-box standard objects you will need to create a lookup field on the HelloSign Signature Request object.
- [2. Create VF page for the Object](https://sfdc-docs.hellosign.com/docs/2-create-vf-page-for-the-object.md)
- [3. Create a Use Dropbox Sign button](https://sfdc-docs.hellosign.com/docs/3-create-a-use-hellosign-button.md)
- [4. Add Use Dropbox Sign button the page layout(s)](https://sfdc-docs.hellosign.com/docs/4-add-use-hellosign-button-the-page-layouts.md)
- [5. Configure the Object in the HelloSign Settings Tab](https://sfdc-docs.hellosign.com/docs/5-configure-the-object-in-the-hellosign-settings-tab.md)
- [6. Configure Permission Sets and Grant Users access](https://sfdc-docs.hellosign.com/docs/6-configure-permission-sets-and-grant-users-access.md): In step two you created a visualforce page. You will need to grant your HelloSign users access to this page.
- [Working with Text Tags](https://sfdc-docs.hellosign.com/docs/working-with-text-tags.md): Text Tags allow you to add HelloSign signature fields, custom fields, and merged Salesforce data directly into the source document. Applying the following syntax to your source file will enable HelloSign to detect the text tags in the document and display them correctly for all signers. Common use cases for Text Tags of when using a third-party document generation tool, or a product like Salesforce CPQ in which templates are built using HTML that gets converted into a PDF document.
- [Text Tags Syntax](https://sfdc-docs.hellosign.com/docs/text-tags-syntax.md)
- [Text Tags - API Name & Case Sensitive](https://sfdc-docs.hellosign.com/docs/text-tags-api-name-case-sensitive.md)
- [Text Tags - Exceptions](https://sfdc-docs.hellosign.com/docs/text-tags-exceptions.md)
- [Text Tag Example 1: Two Signers with HelloSign Text Tags](https://sfdc-docs.hellosign.com/docs/text-tag-example-1-two-signers-with-hellosign-text-tags.md)
- [Text Tag Example 2: Single Signer with Salesforce merge and writeback](https://sfdc-docs.hellosign.com/docs/text-tag-example-2-single-signer-with-salesforce-merge-and-writeback.md)
- [Salesforce Communities](https://sfdc-docs.hellosign.com/docs/salesforce-communities.md): HelloSign supports two options for supporting signature requests within Salesforce Communities: Flow Component & Lightning Component.
- [Communities via Flow](https://sfdc-docs.hellosign.com/docs/communities-via-flow.md)
- [Communities via Lightning Component](https://sfdc-docs.hellosign.com/docs/communities-2.md): HelloSign supports two options for supporting signature requests within Salesforce Communities.
- [Guest User Access](https://sfdc-docs.hellosign.com/docs/external-user-access.md)
- [Dropbox Sign Flow Component](https://sfdc-docs.hellosign.com/docs/hellosign-flow-component.md)
- [Custom Apex SDK](https://sfdc-docs.hellosign.com/docs/sdk.md): HelloSign for Salesforce includes an SDK to extend the product's functionality with your own custom Apex.
- [Quick Start: Send with Template](https://sfdc-docs.hellosign.com/docs/quick-start-send-with-template.md)
- [Get Signature Request](https://sfdc-docs.hellosign.com/docs/sdk-get_signature_request.md): Gets a SignatureRequest that includes the current status for each signer.
- [List Signature Requests](https://sfdc-docs.hellosign.com/docs/sdk-list-signature-requests.md): Lists the SignatureRequests (both inbound and outbound) that you have access to.
- [Send Signature Request](https://sfdc-docs.hellosign.com/docs/sdk-send-signature-request.md): Creates and sends a new SignatureRequest with the submitted documents
- [Send with Template](https://sfdc-docs.hellosign.com/docs/sdk-send-with-template.md): Creates and sends a new SignatureRequest based off of the Template specified with the template_id parameter.
- [Send Request Reminder](https://sfdc-docs.hellosign.com/docs/sdk-send-request-reminder.md): Sends an email to the signer reminding them to sign the signature request.
- [Update Signature Request](https://sfdc-docs.hellosign.com/docs/sdk-update-signature-request.md): Updates the email address for a given signer on a signature request.
- [Cancel Signature Request](https://sfdc-docs.hellosign.com/docs/sdk-cancel-signature-request.md): Cancels an incomplete signature request. This action is not reversible.
- [Get Signature Request Files](https://sfdc-docs.hellosign.com/docs/sdk-get-files.md): Obtain a copy of the current documents specified by the signature_request_id parameter
- [Release On-Hold Signature Request](https://sfdc-docs.hellosign.com/docs/sdk-release-hold.md): Releases a held SignatureRequest that was claimed and prepared from an UnclaimedDraft
- [Create Embedded Unclaimed Draft](https://sfdc-docs.hellosign.com/docs/sdk-create-embedded-unclaimed-draft.md): Creates a new Draft that can be claimed and used in an embedded iFrame
- [Create Embedded Unclaimed Draft With Template](https://sfdc-docs.hellosign.com/docs/sdk-create-embedded-unclaimed-draft-with-template.md): Creates a new draft with a previously saved template that can be claimed and used in an embedded iFrame
- [How to Open an Embedded Claim URL](https://sfdc-docs.hellosign.com/docs/how-to-open-a-claim-url.md)
- [Create Unclaimed Draft](https://sfdc-docs.hellosign.com/docs/sdk-create-unclaimed-draft.md): Creates a new Draft that can be claimed using the claim URL
- [Unit Tests](https://sfdc-docs.hellosign.com/docs/unit-tests.md)
- [Attachment_x](https://sfdc-docs.hellosign.com/docs/attachment_x.md)
- [CC](https://sfdc-docs.hellosign.com/docs/cc.md)
- [CustomField](https://sfdc-docs.hellosign.com/docs/customfield.md)
- [FieldOptions](https://sfdc-docs.hellosign.com/docs/fieldoptions.md)
- [FileUrl](https://sfdc-docs.hellosign.com/docs/fileurl.md)
- [FormField](https://sfdc-docs.hellosign.com/docs/formfield.md)
- [ListInfo](https://sfdc-docs.hellosign.com/docs/listinfo.md)
- [Signature](https://sfdc-docs.hellosign.com/docs/signature.md)
- [SignatureRequest](https://sfdc-docs.hellosign.com/docs/signaturerequest.md)
- [SignatureRequestListResponse](https://sfdc-docs.hellosign.com/docs/signaturerequestlistresponse.md)
- [SignatureRequestResponse](https://sfdc-docs.hellosign.com/docs/signaturerequestresponse.md)
- [Signer](https://sfdc-docs.hellosign.com/docs/signer-1.md)
- [SigningOptions](https://sfdc-docs.hellosign.com/docs/signingoptions.md)
- [UnclaimedDraft](https://sfdc-docs.hellosign.com/docs/unclaimeddraft.md)
- [UnclaimedDraftResponse](https://sfdc-docs.hellosign.com/docs/unclaimeddraftresponse.md)
- [Warning](https://sfdc-docs.hellosign.com/docs/warning.md)
- [Getting Started with Dropbox Sign for Salesforce CPQ](https://sfdc-docs.hellosign.com/docs/getting-started-with-hellosign-for-cpq.md): This section walks through the configuration steps required to implement the HelloSign for CPQ extension package.
- [Install Dropbox Sign for CPQ extension package](https://sfdc-docs.hellosign.com/docs/install-hellosign-for-cpq-extension-package.md)
- [Configure CPQ Quote Template object](https://sfdc-docs.hellosign.com/docs/configure-cpq-quote-template-object.md): The only layout necessary for HelloSign for CPQ are those used by the Quote Template object. The following steps outline adding the “Link HelloSign Template” button and “HelloSign Template” related list to the layout.
- [Configure CPQ Setting](https://sfdc-docs.hellosign.com/docs/configure-cpq-setting.md): Salesforce CPQ enables e-signatures via a plugin setting. The following steps show how to add our plugin in CPQ. If you don’t need the steps here is the plugin “HelloSign_CPQ.eHelloSignPlugin“
- [Assign CPQ Extension Permission Set](https://sfdc-docs.hellosign.com/docs/assign-cpq-extension-permission-set.md): The HelloSign for salesforce CPQ extension package contains a permission set which grants access to several new fields needed to access the CPQ objects. Access must be granted to those HelloSign users who will be using it with salesforce CPQ.
- [Linking a CPQ Quote Template](https://sfdc-docs.hellosign.com/docs/linking-a-cpq-quote-template.md): Linking your existing CPQ Quote Templates allows you to leverage HelloSign signer roles and later send them for e-signature via HelloSign. HelloSign Templates connected to CPQ Quote Templates are considered external templates and are not stored in the HelloSign app.
- [Configure CPQ Template Section Records](https://sfdc-docs.hellosign.com/docs/configure-cpq-template-section-records.md): If a HelloSign Template is linked to a CPQ Quote Template you must add the custom CPQ Template Content record that HelloSign automatically generated. If there are no additional customizations to your quote you will need to additionally add sections for the Header, Quote Terms, and Line Items. The following steps walk through this process.
- [Modify/Style Dropbox Sign Signature Content record](https://sfdc-docs.hellosign.com/docs/modifystyle-hellosign-signature-content-record.md): Out-of-the-box, the HelloSign Signature Template Content record is styled to align with CPQ’s out-of-the-box quote. The HelloSign Signature Content record generated upon linking a CPQ Quote Template to a HelloSign template is generated using html. Those familiar with html can modify the Content record to align with customizations to your CPQ template.
- [Archiving a Template associated with CPQ Quote Template](https://sfdc-docs.hellosign.com/docs/archiving-a-template-associated-with-cpq-quote-template.md): These steps show you how to archive a HelloSign Template and update the associated CPQ Quote Template.
- [Unarchiving a CPQ Template](https://sfdc-docs.hellosign.com/docs/unarchiving-a-cpq-template.md): These are the steps to unarchive a HelloSign Template associated with a CPQ Quote Template.
- [Send CPQ Quote Documents for Signature with HelloSign](https://sfdc-docs.hellosign.com/docs/send-cpq-quote-documents-for-signature-with-hellosign.md): HelloSign for CPQ supports sending signatures with both our templates as well as one-time requests. Below we provide an overview of how both flows work.
- [Send for Signature with Dropbox Sign Template](https://sfdc-docs.hellosign.com/docs/send-for-signature-with-hellosign-template.md): Once linked, CPQ Quote Templates can be sent via HelloSign for e-signature. Using a CPQ Quote Template linked to a HelloSign template supports multiple signers, with predefined roles, a default title and message, and signature fields automatically mapped on the quote document.
- [Send for Signature with Dropbox Sign One-Time Send](https://sfdc-docs.hellosign.com/docs/send-for-signature-with-hellosign-one-time-send.md): Once linked, CPQ Quote Templates can be sent via HelloSign for e-signature. CPQ Quote Templates not linked to a HelloSign Template support multiple signers, but does not support predefined roles, or default title and message. Users must manually map signature fields onto the quote document.
- [HelloSign for Salesforce 4.28](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-428.md)
- [HelloSign for Salesforce 4.27](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-427.md)
- [HelloSign for Salesforce 4.26](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-426.md)
- [HelloSign for Salesforce 4.25](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-425.md)
- [HelloSign for Salesforce 4.24](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-424.md)
- [HelloSign for Salesforce 4.23](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-423.md)
- [HelloSign for Salesforce 4.22](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-422.md)
- [HelloSign for Salesforce 4.21](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-421.md)
- [HelloSign for Salesforce 4.20](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-420.md)
- [HelloSign for Salesforce 4.19](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-419.md)
- [HelloSign for Salesforce 4.18](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-418.md)
- [HelloSign for Salesforce 4.17](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-417.md)
- [HelloSign for Salesforce 4.16](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-416.md)
- [HelloSign for Salesforce 4.14](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-414.md)
- [HelloSign for Salesforce 4.12](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-412.md)
- [HelloSign for Salesforce 4.11](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-411.md)
- [HelloSign for Salesforce 4.10](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-410.md)
- [HelloSign for Salesforce 4.9](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-49.md)
- [HelloSign for Salesforce 4.8](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-48.md)
- [HelloSign for Salesforce 4.7](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-47.md)
- [HelloSign for Salesforce 4.6](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-46.md)
- [HelloSign for Salesforce 4.5](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-45.md)
- [HelloSign for Salesforce 4.4](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-44.md)
- [HelloSign for Salesforce 4.3](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-43.md)
- [HelloSign for Salesforce 4.2](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-42.md)
- [HelloSign for Salesforce 4.1](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-41.md)
- [HelloSign for Salesforce 4.0](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-40.md)
- [HelloSign for Salesforce 3.77](https://sfdc-docs.hellosign.com/docs/2.md)
- [HelloSign for Salesforce 3.76](https://sfdc-docs.hellosign.com/docs/3.md)
- [HelloSign for Salesforce 3.75](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-375.md)
- [HelloSign for Salesforce 3.74](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-374.md)
- [HelloSign for Salesforce 3.72](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-372.md)
- [HelloSign for Salesforce 3.71](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-371.md)
- [HelloSign for Salesforce 3.69](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-369.md)
- [HelloSign for Salesforce 3.68](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-368.md)
- [HelloSign for Salesforce 3.66](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-366.md)
- [HelloSign for Salesforce 3.58](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-358.md)
- [HelloSign for Salesforce 3.51](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-351.md)
- [HelloSign for Salesforce 3.40](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-340.md)
- [HelloSign for Salesforce 3.10](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-310.md)
- [HelloSign for Salesforce 3.05](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-305.md)
- [HelloSign for Salesforce 3.0.1](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-301.md)
- [HelloSign for Salesforce 3.0](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-30.md)
- [HelloSign for Salesforce 2.4](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-24.md)
- [HelloSign for Salesforce 2.1](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-21.md)
- [HelloSign for Salesforce 2.0](https://sfdc-docs.hellosign.com/docs/hellosign-for-salesforce-20.md)
- [Release Cadence](https://sfdc-docs.hellosign.com/docs/release-cadence.md)