Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

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.

Note: A Platform user is not the same as a Sign user. All Sign users are Platform users, but not all Platform users are Sign users. In Salesforce terms, creating a Platform user is similar to adding a user to Salesforce, while creating a Sign user is like assigning a license to a Conga product.

User Creation Method

There are two methods to create a Platform user, either manually or using the auto-provisioning method.

Manual Method

  1. Log in to the Conga Advantage Platform.

  2. Navigate to Admin Console and select Users.

  3. Click Add on the Users page.

  4. Complete the following required fields:

    1. First name

    2. Last name

    3. Email address

    4. Username
      Note: It is recommended (but not required) to use the same value for both the email and username fields for consistency.
  5. Federation ID

    1. Enter the 18-character Salesforce User ID for this user.

    2. Retrieve it from the Salesforce Developer Console using the following SOQL query:
      SELECT Id FROM User WHERE Name LIKE '[FirstName] [LastName]'
    3. 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.

  6. Assign a Role

    1. Select either of the following roles:

      1. Admin ( ensure the Conga Sign Permissions permission group is also assigned)

      2. Conga Sign Integration User

  7. Click Save.

Auto-Provisioning Method

  1. Log in to the Conga Advantage Platform.

  2. Navigate to the Admin Console and select Organization and click Edit.

  3. Enable the Auto Provision User toggle.

  4. Click Save.

  5. Navigate to the External Integrations tab.

  6. Verify that your Salesforce IDP is set as the default:

    1. If not, edit the integration and enable the Default IDP option.

    2. If you do not see a Salesforce IDP record you can create one by following the steps below:

      1. Log out of the Conga Advantage Platform.

      2. Log into the Conga Advantage Platform using your Saleforce credentials via the Salesforce IDP.

      3. 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

  1. Log in to the Conga Advantage Platform.

  2. Navigate to the Admin Console and select Organization.

  3. Go to the External Integrations tab and click Add New.

  4. Choose the appropriate environment:

    1. For a Salesforce Production environment, select Salesforce.

    2. For a Salesforce Sandbox environment, select Salesforce Sandbox.

  5. Click Authorize.

  6. Log in to the Salesforce environment you want to use as your Identity Provider (IDP).

  7. In the Type field, enter:

    1. Prod for Salesforce

    2. Sandbox for Salesforce Sandbox

  8. Enable the Default IDP toggle.

  9. Click Save.

Assigning Permissions

Managing User roles on the Conga Advantage Platform for Conga Sign

The Conga Advantage platform provides flexible role management to suit different user needs. You can assign users to pre-configured roles or create custom roles tailored to your organization.
  • 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.

Auto-Provisioned Users: Users created through auto-provisioning are automatically assigned the AuthAutoProvisionedUser role. This role is intentionally limited in permissions, giving administrators the ability to define what these users can access upon creation.
Attention: The AuthAutoProvisionedUser role must be updated with Conga Sign permissions for users to successfully access Sign functionality on the Platform.
Updating the AuthAutoProvisionedUser Role
  1. Log in to the Conga Advantage Platform.

  2. Navigate to the Admin Console and select Users.

  3. Go to the Roles tab and open the AuthAutoProvisionedUser role.

  4. Click Edit.

  5. In the Permissions Group dropdown, select Conga Sign Permissions.

  6. In the Admin Permissions dropdown, select View Document Management Application.

  7. Click Save.

Assigning Manager Rights to a Sign User

If a user needs the ability to make changes within Conga Sign Settings, they must be granted Manager Rights under the User Management tab.
Note: This step is not required if the user will only be sending transactions.

To grant Manager Rights:

  1. Log in to the Conga Advantage Platform.

  2. Navigate to the Document Management Apps application.

  3. In the left-hand toolbar, select Sign Settings.

  4. Go to the User Management tab and locate the user you wish to grant access to.

  5. 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.

Prerequisites: Designated specific Salesforce user to act as the connector user.
Important: If a designated connection user is not created, logging into Salesforce and the platform repeatedly will cause the connection to break.

Steps:

  1. Login to the Conga Advantage Platform

  2. Navigate to the Document Management Application.

  3. Select Sign Settings from the left sidebar.

  4. Click the Data Sync Connections tab.

  5. Click Connect next to your Salesforce IDP option.

    1. If successful, a green "Connected" message will appear.

    2. 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:

PurposeConga Sign Professional TagConga 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:

ParameterForegroundBackground
&TemplateIdRequiredRequired
&OFNOptionalOptional
&DS7Required (1143)Required (1144)

&CSRecipient[1–20]

OR

&CSName[1-20] &CSEmail[1-20]

RequiredRequired
&CSPackageNameRequiredRequired
&CSTemplateIdOptionalOptional
&idpRequiredRequired
&idporgidRequiredRequired
&idprecordtypeRequiredRequired
&idprecordidRequiredRequired
Base Composer Button URL:
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]
PlaceholderDescription
[Host Environment]

Corresponds to the Conga Advantage Platform environment you're connected to:

• Production: https://composer.congamerge.com

• Preview: https://preview-composer.congamerge.com

[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.
Sample Composer Button URL:
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
&idpRequired
&idprecordidRequired
Base View Transactions Button URL:
https://[Host Environment].congacloud.com/sign-connector/viewtransactions
?idp=[Salesforce Environment Type]
&idprecordid=[Record Id]
PlaceholderDescription
[Host Environment]

Corresponds to the Conga Advantage Platform environment you're connected to:

  • Production: https://production-rls10

  • Preview: https://preview-rls09

[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.
Sample View Transactions Button URL:
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 NameRequired Permissions
Activity HistoryView All
App GroupsView All, Modify All
ConfigurationView All, Modify All
Sign SessionView All, Modify All
ESignTransactionView All, Modify All
Document MetadataView All, Modify All
ListenerCustomerRegistrationView All, Modify All
CongaSignEventView All, Modify All
SignPackageMetadataView All, Modify All
SignConnectorWritebackMappingConfigurationView All, Modify All
ESignRecipientView All
AppRegistryView All
customcodeView All, Modify All
CustomerCallbackView All, Modify All
SignConnectorTransactionView All, Modify All
Issues with the permissions group are rare, but should they occur, these permissions ensure full function