- 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.
- To edit Profile permissions, navigate to Setup > Manage Users > Profiles.
We recommend cloning the Standard User Profile and using that as the Profile you customize and assign to your Composer users.
- For every Profile that will run Composer, check the following:
- Minimum of Read Access to all custom Conga Objects (Conga Email Templates, Conga Global Merges, Conga Queries, Conga Solutions, Conga Solution Email Templates, etc.)
- 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)
- Create permissions to the Documents Object are needed if the user is going to utilize email functionality in Composer
- 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)
- Navigate to Setup > Security Controls > Session Settings and ensure Lock sessions to the IP address from which they originated is NOT enabled.
To use Composer OAuth buttons, users must have APXTConga4.Conga_Composer Visualforce page added in their profile's Enabled Visualforce Page Access section. If this is not included, they will get an Insufficient Privileges error.