This topic describes the Composer Profile Permissions configuration using the Salesforce Standard View.

Navigate to Salesforce Setup → Administration → Users → Profiles > Select the Profile Name you want to change (e.g. Business Analyst) → Edit.

You must review and change the following permissions and access settings:

Custom App Settings

Select the following checkboxes to make them visible. This is not required but enabling it will allow the profile to see the Conga® apps in the Salesforce Custom App menu.

  • Conga Composer
  • Conga Batch® (if Conga Batch is installed)
  • Conga Trigger® (if Conga Trigger is installed)

Connected App Access

If the profile is using the Conga Composer OAuth buttons, enable Conga Composer as a Connected App by selecting the check box.

Tab Settings

Custom Tab Settings - "Default On" is the recommended setting, however, is not require permission for end-users; enabling it will simply allow a user to see the Conga tabs. We do require this permission for System Administrators, as it is needed for maintenance and troubleshooting of solutions.

  • About Conga Composer
  • Conga Composer Setup
  • Conga Templates
  • Conga Email Templates
  • Conga Queries
  • Conga Resources


If Conga Batch is installed, we recommend enabling its tabs as "Default On." These tabs are required as "Default On" for System Administrators.

  • About Conga Batch
  • Conga Batches
  • Conga Batch Setup
  • Conga Batch Dashboard


If Conga Trigger is installed, we recommend enabling its tabs as "Default On." These tabs are required as "Default On" for System Administrators.

  • About Conga Trigger
  • Conga Trigger Setup
  • Conga Trigger Formula Builder
  • Conga Trigger Dashboard

Administrative Permissions

Select the API Enabled check box. This is required permission for anyone using Conga Composer.

  • API Enabled

General User Permissions

Select the following checkboxes; both are required for any users who are using reports as part of their Conga Composer solutions.

  • Export Reports
  • Run Reports

Standard Object Permissions

Create permission is required on the Documents object in order for a user to utilize email functionality with Conga Composer. Delete permission is also highly recommended for the Documents object.

The Documents object is used in Conga Composer as a temporary holding area for the merged output file while the email is assembled. The Create permission allows a user to utilize this functionality while the Delete permission ensures that each document that is created by a user has subsequently replaced the next time that user initiates a Conga Composer email process.

Custom Object Permissions

Provide at least Read access (Create, Edit, Delete, View All, and Modify All are not required for end-users and can be enabled at your discretion) for the following objects. Read, Create, Edit, and Delete permissions are required for Conga Email Staging.

  • Conga Templates℠ - Conga Templates is a custom object that allows you to store your document (Word®, Excel®, PowerPoint®, or PDF) templates.

  • Conga Email Templates℠ - Conga Email Templates is a custom object that allows you to build and store HTML email templates for use in your merge operation, whether as the primary destination for merged data or used in conjunction with a document template.

  • Conga Email Staging℠ - requires Read, Create, Edit, and Delete permissions.

    Note: Conga Email Staging is a component of Conga Email; Read, Create, Edit, and Delete permissions are required for any profile using Conga Email

  • Conga Queries℠ - Conga Queries is a custom object that allows you to build and store SOQL queries to retrieve data for use in your merge operation.

  • Conga Batch (if Conga Batch is installed) - Conga Batch is an optional, paid add-on to Conga Composer that launches on-demand or scheduled Conga Composer solutions in batches.
  • Conga Trigger (if Conga Trigger is installed) - Conga Trigger is an optional, paid add-on to Conga Composer that launches Conga Composer operations as the result of a Salesforce Conga Trigger rule.
  • Scheduled Conga Batch History℠ (if Conga Batch is installed) - Scheduled Conga Batch History is a child object of Conga Batch and displays details of past scheduled Conga Batch routines.]
In addition to providing access to Objects, ensure Profiles have access to all necessary fields on the custom Conga Objects as well as fields on other Objects from which you are merging data.

Enabled Custom Setting Definitions

Click Edit under the Enabled Custom Setting Definitions Access section and add the following Available Custom Setting Definitions to Enabled Custom Setting Definitions.

  • Composer
    • Conga Composer.APXTConga4.Conga Composer Settings
    • Conga Composer.APXTConga4.Conga Solutions Settings

Enabled Custom Metadata Type Access

Click Edit under the Enabled Custom Metadata Type Access section and add the following Available Custom Metadata Types to the Enabled Custom Metadata Types. After adding the Custom Metadata Types, click Save.

  • Composer
    • APXTConga4.Composer Setting
    • APXTConga4.Conga Solution Export Environment
    • APXTConga4.Conga Solution Export Setting
    • APXTConga4.Connected App Setting
  • Batch (if Conga Batch is installed)
    • APXT_BPM.Conductor Region
    • APXT_BPM.Conductor Setting
  • Trigger (if Conga Trigger is installed)
    • CongaWorkflow.Workflow Region
    • CongaWorkflow.Workflow Setting