Skip to main content
Conga Support

Basic Settings and configuring Composer

Conga Composer Setup

You can change various user management, integration and basic settings in Conga® by visiting the Conga Setup page, which is accessible from Salesforce® Setup > Installed Packages and Configure next to Conga Composer®  (see below).

The Conga Setup link also appears on the Conga Composer dialog box, under the Tools & Settings drop-down menu for users who have the following permissions:

  • View All Data
  • Modify All Data
  • View Setup

Under the Basic tab, you can change the default settings for local template usage, template manager repositories and solution behaviors. You must ensure that the following items are selected:

  • Under the Conga Template Manager: Select Enable the new, built-in Conga Template Manager
  • Offline Access: Click Update Salesforce Token
  • Behavior Modifications: Ensure all items are selected.

Allow Use of Local Templates

By default and as a recommended practice, only users with the Salesforce® System Administrator profile are permitted to upload a template from their local hard drives. This feature is always enabled for administrators because of its utility in creating and testing templates. You may enable this feature for all other user profiles by checking the box to permit users to upload a template from a local drive.

Local templates can also be enabled on a solution-by-solution basis via the Conga Composer® parameter &DS8=1. Visit the Conga Composer Index of Parameters for more information.

Conga Template Manager

Instead of using the Salesforce Communication Templates repository, we strongly recommend that you store templates in the Conga Template Manager℠ (see Storing Merge Templates for details). This custom object is included in the Conga Composer application so does not require separate installation.

Behavior Modification

The Behavior Modification settings govern how Conga® retrieves data and how templates behave. If your organization is new to Conga, we strongly recommend that you enable all of the Behavior Modification settings.

If your organization is upgrading to Release 8 from Conga Composer 1.6 or earlier (or any version where you previously did not have these settings enabled), you may now enable these settings, however, they may affect your templates – proceed with caution.

Query Object Name Correction

This setting corrects a problem in which Conga Queries resulted in object names with double underscores. For example, a merge field name for the Amount field on an Opportunity sometimes appeared as:


Instead of


This was an issue because modifying the Conga Query sometimes resulted in slightly different field names, thus preventing a merge field from working properly.

Prevent Auto-Incrementing Column Name

This setting corrects a merge field naming problem in Reports and Queries in which column names were appended with “_1” to delineate multiple instances of the merge field across the entire dataset.

Word Templates: Require TableStart/TableEnd for Detail Regions

This setting makes it necessary to use TableStart/TableEnd to access detail data, which is important because some customers have unintentionally discovered that Conga Composer would generate a separate document for each row of detail data in the absence of a TableStart/TableEnd.

In Conga Composer Release 8, all templates require TableStart and TableEnd in order to merge detail data, regardless of whether this checkbox is checked.

Simple Report Column Names

This setting prevents Conga from altering field names used in Reports and Queries when a Salesforce ID column is also referenced in the Report or Query.

Enable Text-based Merge Fields (Word)

This setting enables text-based merge fields in Microsoft Word templates. If this setting is not enabled only Microsoft Word® traditional merge fields are available.

Text-based merge field: {{ACCOUNT_NAME}}
Traditional merge field: «ACCOUNT_NAME»