A profile in Salesforce is a group/collection of settings and permissions that define what a user can do in Salesforce. A profile controls “Object permissions, Field permissions, User permissions, Tab settings, App settings, Apex class access, Visualforce page access, Page layouts, Record Types, Login hours & Login IP ranges". You can define profiles by user’s job function. For example, System Administrator, Developer, Sales Representative. A profile can be assigned to many users, but a user can be assigned a single profile at a time. 

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

You must ensure the following permissions and access settings are set correctly:

  1. When installing Conga Composer from the AppExchange, select Install for All Users. If you did not initially install Composer for all users, you will need to modify the field level security for each field on the custom Conga Objects.

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

    It is highly suggested to clone the Standard User Profile and use that as the Profile you customize and assign to your Composer users. According to Salesforce, a user assigned to a standard profile cannot view any custom object, as opposed to a custom profile which allows users to view custom objects.

  3. For every Profile that runs Composer:
    • Minimum of Read Access to all custom Conga Objects (Conga Email Templates, Conga Global Merges, 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). Minimum of Create permission to the Documents Object is needed if the user is going to utilize email functionality in Composer.

      You can also use the Permission Sets to grant additional access or temporary access to a specific set of fields and objects as per your business use cases.

    • Check API Enabled under Administrative Permissions.
    • Check Run Reports and Export Reports (if you are using reports with your Composer solutions) and also ensure the report folders that contain your Composer reports are shared with end-users.
    • Configure Composer as a Connected App for any Profiles that will use the OAuth button (this is required to use Conga Composer in the Salesforce Lightning interface).

    • If you save output data to chatter, update System Settings to check Moderate Chatter.

      To use Composer OAuth buttons, users must have the APXTConga4.Conga_Composer Visualforce page added in their profile's Enabled Visualforce Page Access section. If this is not included, users receive an Insufficient Privileges error.
    • Enable Custom Setting Definitions Access
      • Composer
        • Conga Composer.APXTConga4.Conga Composer Settings
        • Conga Composer.APXTConga4.Conga Solutions Settings
    • Enable Custom Metadata Type Access
      • 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
  4. Navigate to Setup → Security Controls → Session Settings and ensure that Lock sessions to the IP address from which they originated is not enabled.

For more detailed information about setting up Profile permissions for the Standard and Enhanced View, see the following:

When you are ready to start building solutions, see Composer Basics.

You can use the PermComparator tool to troubleshoot differences between Salesforce profiles.