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.

Conga Batch Permission Requirements

This topic describes the minimum levels of permission and access settings required for a Conga Composer user to successfully run Conga Batch.

You will need to create a working Composer solution, as listed in Working Composer Solutions. You will need to be a Composer Administrator and have an operational Composer license.

Permission Requirements for Batch

To edit Profile permissions, navigate to Setup > Manage Users > Profiles.

Add the following permissions:
  • Minimum of Read Access to all custom Conga Objects (Conga Email Templates, Conga Queries, Conga Solutions, Conga Solution Email Templates).
  • Minimum of Read Access to ALL Objects and Fields included in the merge templates (keep in mind the most restrictive settings apply, so if a user has visibility to a field but not the Object, they will not be able to merge data from that field).

Assign the following permission set to your Batch users:

Batch Administrator

This will include the following permissions:

Visualforce Page Access
  • APXT_BPM.Conductor_Launch

  • APXT_BPM.Conductor_Schedule

  • APXT_BPM.ConductorDashboardButtonPage

  • APXT_BPM.ConductorDashboardPage

  • APXT_BPM.ConductorSetupPage

  • APXT_BPM.FormulaBuilderPage

Apex Class Access
  • APXT_BPM.CNMockHttpResponseGenerator

  • APXT_BPM.Conductor_CtlExt

  • APXT_BPM.Conductor_CtlExt_Test

  • APXT_BPM.ConductorUrlController

  • APXT_BPM.ConductorUrlController_Test

Custom Metadata Types
  • APXT_BPM.Conga Batch Region

  • APXT_BPM.Conga Batch Setting