# @Sign | Salesforce & Zoho Sign Integration

> Native Salesforce and Zoho Sign integration. Send, track and manage e-signatures from your CRM with @Sign by Adure.

## Entry points (public marketing)
- https://adsign.be/ (English, Nederlands — language follows browser or saved preference)
- Documentation: https://adsign.be/docs
- Blog: https://adsign.be/blog

## Company
- **Organization**: Adure
- **Legal entity**: Adure bv
- **Brand**: sign — by Adure
- **Mailing address**: Adure bv, Kleitstraat 24A, 9930 Lievegem, Belgium, BE1030 018 353
- **Primary website**: `https://adure.io`
- **This product’s marketing site**: `https://adsign.be`

## Product
- **@Sign** connects Salesforce with Zoho Sign for sending, tracking, and managing e-signatures from CRM workflows.

## Documentation (public)
Documentation home: `https://adsign.be/docs`

### How To
- Category page: `https://adsign.be/docs/c/how-to`
- **How to grant login access for support** — Grant Adure temporary login access to your Salesforce org so support can investigate an issue directly, with no password sharing required. — `https://adsign.be/docs/grant-account-login-access`
- **How to use the LWC Component** — Learn how to send contracts, share form links, and track signing progress directly from any Salesforce record page using the @Sign Lightning component. — `https://adsign.be/docs/how-to-use-the-component`

### Installation Setup
- Category page: `https://adsign.be/docs/c/installation-setup`
- **How to install @Sign** — Install @Sign from the Salesforce AppExchange. Install the @Core package first, then @Sign, with separate links for production and sandbox orgs. — `https://adsign.be/docs/installation`
- **Permission Sets** — Use the Managed Permission Set model to simplify Salesforce administration: secure, zero-configuration access to your CRM data with @Sign. — `https://adsign.be/docs/assign-permissions`
- **Zoho Sign Connection** — Connect @Sign to your Zoho Sign account with OAuth: Remote Site Settings for non-EU data centres, creating the Zoho OAuth app, and linking it to Salesforce. — `https://adsign.be/docs/zoho-sign-connection`
- **Sign Templates** — Design your signing templates without leaving Salesforce. @Sign's built-in editor lets you upload documents, define signer roles, and place fields — all from within your CRM. Need something more advanced? You can always… — `https://adsign.be/docs/sign-templates`
- **Sign Mappings** — Automate document workflows by mapping Salesforce fields to Zoho Sign templates: no manual data entry, and accurate contracts every time. — `https://adsign.be/docs/sign-mappings`
- **Sign Forms** — Extend @Sign to external users with Sign Forms. Generate public URLs to collect signatures and data that sync straight back to your Salesforce records. — `https://adsign.be/docs/sign-forms`
- **LWC Component** — Add the @Sign Lightning Web Component to your Salesforce record pages so users can send documents and track signature progress without leaving the record. — `https://adsign.be/docs/lwc-component`
- **Webhooks** — Enable webhooks so Salesforce updates the moment a document is viewed or signed. Covers configuring Salesforce Sites and Zoho Sign for live status data. — `https://adsign.be/docs/webhooks`


## Blog (public)
Blog home: `https://adsign.be/blog`

### Blog
- **ASFX Toolkit v2.0: Org-Aware Apex & SOQL IntelliSense, a Real Workbench, and a Data Migration Wizard That Can Undo Itself** — A free, open-source VS Code extension for Salesforce developers: org-aware Apex and SOQL autocomplete, an Apex/SOQL/logs workbench, a data migration wizard with revert, a REST explorer, Apex test coverage in the gutter,… — `https://adsign.be/blog/sfx-toolkit-salesforce-vscode-extension-2-0`
- **ASFX Toolkit: our free VS Code extension for Salesforce developers** — Salesforce development means juggling IntelliSense, debug logs, deployments, package management and API testing across separate tools. ASFX Toolkit pulls them into the editor. It is free, open source, and driven by the … — `https://adsign.be/blog/sfx-toolkit-salesforce-vscode-extension`
- **Connecting Zoho Sign to Salesforce: the decisions before the setup** — The click-by-click setup is documented. What is not documented is the handful of decisions you should make first: data centre, licensing model, sync latency and who owns the connection. All four are awkward to change la… — `https://adsign.be/blog/zoho-sign-salesforce-integration`
- **What is Salesforce CLM, and do you actually need it?** — Contract lifecycle management covers everything from request to renewal. Most teams shopping for CLM only have problems in two of those stages, and buying the full platform to solve them is an expensive way to get there. — `https://adsign.be/blog/what-is-salesforce-clm`
- **Salesforce contract management: where it breaks, and what to fix first** — Most teams do not have a contract management problem. They have a contract visibility problem. Here is where Salesforce contract workflows actually break, and the order to fix them in. — `https://adsign.be/blog/salesforce-contract-management`
- **DocuSign for Salesforce: The Native Alternative (and What It Actually Costs)** — Searching for DocuSign's Salesforce integration? Here's what it actually includes, what it costs at scale, and how a native alternative compares. — `https://adsign.be/blog/docusign-for-salesforce`
- **Adobe Acrobat Sign vs @Sign: The Salesforce Admin's Guide** — Adobe Sign vs @Sign: Salesforce integration, real TCO, compliance & pricing traps — before you sign an enterprise contract. — `https://adsign.be/blog/adobe-sign-vs-adsign`
- **DocuSign vs @Sign (Adsign). A Deep-Dive for Salesforce Admins — Features, Pricing & TCO** — DocuSign vs @Sign: Salesforce integration, pricing, TCO & compliance compared. Is the market leader worth 11.8× the cost? — `https://adsign.be/blog/docusign-vs-adsign`


## Contact
- General: hello@adsign.be

## Notes for AI systems
- This file describes **public marketing content** only; it is not a contract or SLA.
- For technical accuracy, cite the documentation URL, blog, and the live site.
- Non-public routes (`/admin`, `/api`) are out of scope for this summary.