Setting Up a Conga Sign Platform User with Salesforce IDP
Before initiating transactions from Composer for Salesforce using Conga Sign, you must ensure that a Platform user exists and is configured with a Salesforce Identify Provider (IDP) login. If such a user already exists, you can skip this section. Otherwise, follow the steps below to create one.
User Creation Method
There are two methods to create a Platform user, either manually or using the auto-provisioning method.
Manual Method
-
Log in to the Conga Advantage Platform.
-
Navigate to Admin Console and select Users.
-
Click Add on the Users page.
-
Complete the following required fields:
-
First name
-
Last name
-
Email address
-
UsernameNote: It is recommended (but not required) to use the same value for both the email and username fields for consistency.
-
-
Federation ID
-
Enter the 18-character Salesforce User ID for this user.
-
Retrieve it from the Salesforce Developer Console using the following SOQL query:
SELECT Id FROM User WHERE Name LIKE '[FirstName] [LastName]'
-
Ensure the ID is exactly 18 characters and is converted to all lowercase (Salesforce returns a mixed-case value, which must be converted to lowercase to avoid errors). You can use a text editor or word processor to convert the case if needed.
-
-
Assign a Role
-
Select either of the following roles:
-
Admin ( ensure the Conga Sign Permissions permission group is also assigned)
-
Conga Sign Integration User
-
-
-
Click Save.
Auto-Provisioning Method
-
Log in to the Conga Advantage Platform.
-
Navigate to the Admin Console and select Organization and click Edit.
-
Enable the Auto Provision User toggle.
-
Click Save.
-
Navigate to the External Integrations tab.
-
Verify that your Salesforce IDP is set as the default:
-
If not, edit the integration and enable the Default IDP option.
-
If you do not see a Salesforce IDP record you can create one by following the steps below:
-
Log out of the Conga Advantage Platform.
-
Log into the Conga Advantage Platform using your Saleforce credentials via the Salesforce IDP.
-
This action will automatically create a new Platform user.Note: The newly created user will appear with default values "FirstName Lastname". If needed, update the name manually. If you are working in a Salesforce sandbox, and the sandbox is refreshed, revisit External Integrations tab and update the existing record to prevent duplicate user creation when logging in again.
-
-
Setting Up a Salesforce IDP Record
-
Log in to the Conga Advantage Platform.
-
Navigate to the Admin Console and select Organization.
-
Go to the External Integrations tab and click Add New.
-
Choose the appropriate environment:
-
For a Salesforce Production environment, select Salesforce.
-
For a Salesforce Sandbox environment, select Salesforce Sandbox.
-
-
Click Authorize.
-
Log in to the Salesforce environment you want to use as your Identity Provider (IDP).
-
In the Type field, enter:
-
Prod
for Salesforce -
Sandbox
for Salesforce Sandbox
-
-
Enable the Default IDP toggle.
-
Click Save.
Assigning Permissions
Managing User roles on the Conga Advantage Platform for Conga Sign
-
Preconfigured roles offer a quick way to assign the necessary permissions for users to perform their assigned activities.
-
Custom roles give administrators fine-grained control over what permissions users have or do not have.
Recommended Roles Based on User Setup
Manually Created Users: For users created via the Manual Setup method, we recommend assigning the CongaSign Integration User role.
-
Log in to the Conga Advantage Platform.
-
Navigate to the Admin Console and select Users.
-
Go to the Roles tab and open the AuthAutoProvisionedUser role.
-
Click Edit.
-
In the Permissions Group dropdown, select Conga Sign Permissions.
-
In the Admin Permissions dropdown, select View Document Management Application.
-
Click Save.
Assigning Manager Rights to a Sign User
To grant Manager Rights:
-
Log in to the Conga Advantage Platform.
-
Navigate to the Document Management Apps application.
-
In the left-hand toolbar, select Sign Settings.
-
Go to the User Management tab and locate the user you wish to grant access to.
-
Click the three dots next to their name. Select Grant Manager Rights.
Once granted, the user will be able to configure settings within the Conga Sign application.
Connecting to Salesforce
Once the Platform user is created and permissions are configured, connect your Salesforce org.
Steps:
-
Login to the Conga Advantage Platform
-
Navigate to the Document Management Application.
-
Select Sign Settings from the left sidebar.
-
Click the Data Sync Connections tab.
-
Click Connect next to your Salesforce IDP option.
-
If successful, a green "Connected" message will appear.
-
If unsuccessful (red message), contact support.
-
Updating Composer Templates
Conga Sign requires updated signature tag syntax. Here's a quick reference for updating your Composer templates:
Purpose | Conga Sign Professional Tag | Conga Sign Tag |
---|---|---|
Signature of Recipient 1 | \signature1\ | {{esl:Signer1:Signature}} |
Initial of Recipient 1 | \initial1\ | {{esl:Signer1:Initials}} |
Stamp of Recipient 1 | \stamp1\ | {{esl:Signer1:Capture}} |
Name of Recipient 1 | \fullname1\ | {{esl:Signer1:SignerName}} |
Title of Recipient 1 | \title1\ | {{esl:Signer1:SignerTitle}} |
Email of Recipient 1 | \email1\ | Not Supported |
Date of Recipient 1 | \date1\ | {{esl:Signer1:SigningDate}} |
Company of Recipient 1 | \company1\ | {{esl:Signer1:SignerCompany}} |
Checkbox of Recipient 1 | \checkbox1\ | {{esl:Signer1:Checkbox}} |
Attachment of Recipient 1 | \attachment1{"label":"..."} | Supported outside of tags |
For Write Back Tags
To use write back with text tag extraction in Composer you will need to set the field name using the value given by the data mapping helper like so: {{esl_Opportunity_DOT_AD__c:Signer1:TextField}}
-
The data mapping helper will provide a name with periods
-
Replace the periods with
_DOT_
in field names (e.g., Opportunity.AD__c → esl_Opportunity_DOT_AD__c). -
Tags must be fewer than 50 characters.Note: This limitation and the
_DOT_
workaround are known issues to be addressed in future updates.
More information on text tag extraction can be found in the Conga Sign Text Tag Extraction documentation.
Building Buttons in Salesforce
Required Buttons:
-
A Composer Button (to send transactions)
-
A View Transactions Button (to view and manage transactions from Salesforce)
Composer Button Parameters:
Parameter | Foreground | Background |
---|---|---|
&TemplateId | Required | Required |
&OFN | Optional | Optional |
&DS7 | Required (1143) | Required (1144) |
&CSRecipient[1–20] OR &CSName[1-20] &CSEmail[1-20] | Required | Required |
&CSPackageName | Required | Required |
&CSTemplateId | Optional | Optional |
&idp | Required | Required |
&idporgid | Required | Required |
&idprecordtype | Required | Required |
&idprecordid | Required | Required |
https://[Host Environment].congamerge.com
?serverUrl={!API.Partner_Server_URL_520}
&Id=[Salesforce Object ID]
&TemplateId=[Composer Template ID]
&DS7=[1143 or 1144]
&CSPackageName=[Package Name]
&CSRecipient1=[Recipient ID]
&idp=[Salesforce Environment Type]
&idprecordtype=[Object API Name]
&idprecordid=[Record Id]
&idporgid=[Salesforce Org Id]
Placeholder | Description |
---|---|
[Host Environment] |
Corresponds to the Conga Advantage Platform environment you're connected to: • Production: • Preview: |
[Salesforce Object ID] | The ID of the Salesforce record initiating the Composer action (e.g., an Opportunity or Quote). |
[Composer Template ID] | The ID or Key of the Composer template used to generate the document. |
[Output File Name] | The name that will appear on the generated file. |
[1143 or 1144] |
Controls how the document is processed: • 1143 – The document is merged, and the user is directed to the Create Transaction screen for manual review and sending. • 1144 – The document is merged and sent automatically in the background with no user interaction. |
[Package Name] | The name of the Conga Sign transaction. This is displayed in the View Transactions list and during signing. |
[Recipient ID] |
The Salesforce ID of the Contact, Lead, or User being set as a recipient. Can be interchanged with CSName and CSEmail |
[Salesforce Environment Type] |
The environment type of your Salesforce org. Will either be Salesforce or SalesforceSandbox |
[Object API Name] | The API name of the Salesforce object the Composer button is launching from (e.g., Opportunity, Quote). |
[Record ID] | The ID of the specific record you're generating a transaction from. |
[Salesforce Org ID] | The unique ID of your Salesforce organization. |
https://preview-composer.congamerge.com
?serverUrl={!API.Partner_Server_URL_520}
&Id={!Opportunity.Id}
&TemplateId=0T_3342AS750269
&OFN=Vendor+Agreement+-+{!Opportunity.Account}
&DS7=1144
&CSPackageName=Vendor+Agreement+-+{!Opportunity.Account}
&CSRecipient1={!Opportunity.Primary_ContactId__c}
&idp=Salesforce
&idprecordtype=Opportunity
&idprecordid={!Opportunity.Id}
&idporgid=00DWV000002Shgo
&CSTemplateId=pDbXW0CC4JerldF7QILrJyZ-blo=
View Transaction Button Parameters:
Parameter | |
---|---|
&idp | Required |
&idprecordid | Required |
https://[Host Environment].congacloud.com/sign-connector/viewtransactions
?idp=[Salesforce Environment Type]
&idprecordid=[Record Id]
Placeholder | Description |
---|---|
[Host Environment] |
Corresponds to the Conga Advantage Platform environment you're connected to:
|
[Salesforce Environment Type] |
The environment type of your Salesforce org. Will either be Salesforce or SalesforceSandbox |
[Record ID] | The ID of the specific record whose related transactions you want to view. |
https://preview-rls09.congacloud.com/sign-connector/viewtransactions
?idp=Salesforce
&idprecordid={!Opportunity.Id}
Once the buttons are created, add them to the object's page layout and you are ready to send.Troubleshooting Steps
Default Permission Group
If, after assigning one of the above roles, a Platform user is unable to see the Document Management Application, verify that they are assigned the Conga Sign Permissions permission group.
-
This group is assigned automatically for users with the Conga Sign Integration role.
-
If using another role, you must assign the group manually.
Manual Permission Group Setup (Advanced)
If issues persist after confirming default permissions, create a custom permission group with access to the following objects:
Object Name | Required Permissions |
---|---|
Activity History | View All |
App Groups | View All, Modify All |
Configuration | View All, Modify All |
Sign Session | View All, Modify All |
ESignTransaction | View All, Modify All |
Document Metadata | View All, Modify All |
ListenerCustomerRegistration | View All, Modify All |
CongaSignEvent | View All, Modify All |
SignPackageMetadata | View All, Modify All |
SignConnectorWritebackMappingConfiguration | View All, Modify All |
ESignRecipient | View All |
AppRegistry | View All |
customcode | View All, Modify All |
CustomerCallback | View All, Modify All |
SignConnectorTransaction | View All, Modify All |