Overview
HelloSign for Salesforce Admin Guide Documentation
Documentation for HelloSign for Salesforce Admin Guide
Content and agent signals
For agents (AI-generated): Admin documentation for Dropbox Sign (HelloSign) for Salesforce: quick start, AppExchange installation, Classic and Lightning compatibility and connection setup
electronic signaturesalesforce integrationdropbox signadmin guideappexchange
Files
Publisher files and the directory’s indexed copy.
Read the cached llms.txt preview
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-30T09:09:35.291Z. Cached copy · Source on hellosign.com
# HelloSign for Salesforce Admin Guide Documentation
> Documentation for HelloSign for Salesforce Admin Guide
## Guides: Documentation
- [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…
- [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…
- [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…
- [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…
- [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…
- [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/ex
…
Published headings
4 indexed headings in this publisher record.
Headings describe indexed content. They do not establish a working integration or endorsement.
Agent access
Review the publisher’s own access terms before automated use.
Machine-readable: GET /v1/resolve?q=hellosign.com · GET /v1/domain/hellosign.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Indexing evidence
Authority, classification and country evidence
Own or manage this website?
If you own or manage hellosign.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free account required for verification and live checks. No backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for hellosign.com:
1. POST https://agentwebmap.com/v1/sites/hellosign.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://hellosign.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/hellosign.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/hellosign.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.