You must refer to the following Authorization and Permission Matrix to run your Conga Composer Solution successfully.

The method of authorization and the permissions needed to execute a merge vary on the basis of the execution point and the method.


Type of AuthenticationConnected AppsPre-Requisites
and
Permissions
Session IDOAuth

JWT

(JSON Web Token)

Composer
NA,EMEA,AP		Composer
SF1, NA, EMEA, AP		Scheduler
Classic SF Button




3, 4
SF Custom Action




3, 4
Lightning Component




1, 2, 3, 4
Orchestrate



3, 4
ServiceUser



3, 4
Trigger

From Outbound Message





3, 4
BatchFrom Refresh Token


3, 4, 6
Community Lightning Component




1, 2, 3, 4
Mobile Custom Action




3, 4
Mobile Lightning Component




1, 2, 3, 4, 7
React Setup Menu



5

Pre-Requisites and Permissions Legend

  1. You must have a My Domain org to use the Lightning Component.
  2. To use the Lightning Component, the users in the org must have read permission to custom metadata types for Composer (and CQG) to read the refresh token stored there (this is in the Composer permission set).
  3. All Composer packages older than version 8.179 "Grays" must provide explicit Read permissions for all Composer users to custom settings and metadata.
  4. If an Admin installs the Conga Composer and selects "For Admins Only" during the installation, then they will need to create a permission set to give their users access to the connected apps and all Composer package components.
  5. Composer_Administrator permission set.
  6. Conga Batch Region Metadata permission is required to run Batch from Grid view.
  7. To use the Lightning Component for SF1, you must have "Modify Metadata Through Metadata API Functions" AND "Customize Application".