The permission set is also very similar to the profile. Whatever you can manage at profiles (Like Object permissions, Field Permissions, User permissions, Tab settings, App settings, Apex class permission, visualforce permission) the same you can manage using permission sets also. But the main difference between these two is that users can have only one profile and can have multiple permission sets at a time. 

In order to grant a very specific ability to a user, you obviously don’t want to create a whole new profile just for that one difference between their abilities and the rest of their team’s! So, you can define profiles to grant minimum permissions and settings that every type of user needs, then you can use the permission set to grant additional access. 

For Example: 

  1. You have many users in your organization with some fundamental job functions. You can assign all of them with one profile that grants them all access to do their job. But some sets of people are working on special apps or some special functionality, for this type of special user you can create permission sets and can be assigned to them. 
    Let’s take an example: There is a sales team, who have the profile ‘Sales User’. Only James should be able to change the team’s email templates, so you as an Admin create a Permission Set called ‘Modify Email Templates’ which you add to James’s user record.
  2. Some users need some temporary access to a specific set of fields and objects you can create a permission set with those objects & field access and you can assign those specific users. 

For more information, see Permission Sets and Permission Set Groups.

Composer Out-of-Box Permission Sets

Conga Composer is installed with the following Permission Sets that you can use for user access and permissions. 

  • Composer_Administrator: Setup permissions for Conga Composer Administrator.
  • Composer_User: Setup permissions for Conga Composer User.
  • Composer_Salesforce_Community_User: Setup permissions for Conga Composer Communities User.

If you want to use the out-of-box permission sets instead of profile level settings, the following are 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. Assign the Composer_User permission set to the Composer user who runs the solutions.
  2. Create and assign a new Permission Set or Profile to the Composer user, and ensure the following permissions and access settings are set correctly:
    1. Check API Enabled under System Permissions.
    2. Check Run Reports and Export Reports under System Permissions (if you are using reports with your Composer solutions) and also ensure the report folders that contain your Composer reports are shared with users.
    3. Check Send Outbound Messages under System Permissions. (Required for the user that initiates the workflow process, otherwise, the email is not sent)
    4. Check APXTConga4.Conga Composer(APXTConga4_CongaMerge) under the Assigned Apps. Click Edit and move APXTConga4.Conga Composer(APXTConga4_CongaMerge) from the Available Apps to the Enabled Apps.

    5. Configure Composer as a Connected App for any Permission Set that will use the OAuth button (this is required to use Conga Composer in the Salesforce Lightning interface).

      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.

  3. 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 use Permission Set to grant additional access or temporary access to a specific set of fields and objects as per your business use cases.

  4. Navigate to Setup → Security Controls → Session Settings and ensure that Lock sessions to the IP address from which they originated is not enabled.

Tab Setting under Profile Permissions:

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

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 the 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

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