Conga Sign Integration Guide
The definitive resource for administrators setting up and configuring Conga Sign for Web (or Sign 2.0) on the Conga Advantage Platform
This guide consolidates all required setup processes into a single required setup processes into a single resource, covering Platform user management, Sign setting configuration, Salesforce integration, transaction button creation, etc. The goal of this guide is to take you from a freshly provisioned Sign account to a fully configured, ready to use Platform environment. Along the say you'll learn not just how to complete each task but also the purpose behind configuration choices.
Who this is For
This guide is written for Conga Advantage Platform administrators who are responsible for setting up and maintaining Conga Sign for their organization. You should have:
Administrator access to the Conga Advantage Platform
Administrator access to your Salesforce organization (if connecting Salesforce)
System Administrator access in Salesforce (if setting up the dedicated connector user or building Salesforce buttons)
Familiarity with basic Salesforce administration concepts such as user management, page layouts, and custom buttons
You do not need to be a developer to follow this guide. The API configuration section is the only portion that assumes technical familiarity with REST APIs.
Initial Platform setup: users, roles, permissions, granting Sign access, and SAML 2.0 SSO configuration
Conga Sign Settings: account configuration, branding, data retention, feature and transaction behavior
Salesforce connector setup: connecting your org, configuring data mapping, and building Salesforce buttons
Composer + Sign integration: setting up the combined Composer and Sign workflow from Salesforce
API-based implementation: overview of the API configuration path; the full developer runbook with Postman collections is available in the Conga Sign REST API documentation
Template configuration: building and managing Sign templates
Troubleshooting and error reference.
eIDAS compliance configuration (SES, AES, QES signature types, Swisscom QTSP setup)
Legacy Sign (Sign Professional) migration to Sign 2.0
Advanced API development beyond the setup walkthrough
End user guidance for sending and managing transactions (covered in the Conga Sign User Guide)
How To Use This Guide
Each section is self-contained and can be referenced independently, but if you are setting up Sign for the first time, we recommend working through the sections in order:
Initial Platform Setup - Complete Platform user setup and Sign Settings configuration. Everything else depends on having users and settings in place.
Template Configuration - Build your templates. Useful for Platform-only setups, and recommended before connecting Salesforce so you have template IDs ready to reference in button configurations.
Salesforce Connector Setup - Set up the Salesforce connector and build your buttons once users, settings, and templates are ready.
Supported Configurations
| Configuration | Description |
|---|---|
| Platform only | Sign is used directly through the Conga Advantage Platform, with no Salesforce integration. Users log in to the Platform to send and manage transactions. |
| Sign + Salesforce connector | Sign is connected to Salesforce, allowing users to initiate transactions and launch the transaction dashboard directly from Salesforce records. |
| Sign + Composer + Salesforce | Conga Composer generates documents from Salesforce data, which are then passed directly to Sign for signature. |
| API-based implementation | Sign transactions are created and managed programmatically via the Conga Sign REST API, with or without a Salesforce integration. |