The following instructions are for your Salesforce System Administrator and not part of the Conga support package.
You can set up Conga Composer to integrate with Salesforce Communities. Here are the steps to integrate Conga All with Salesforce Communities.
Set up community (basic set up – branding, color scheme, header, footer, email templates, chatter branding, login/out URL, notification templates, self-registration settings, customize tabs etc)
- Activate Share Group settings (optional)
- Set up Partner Roles per Partner Account (Partner Portal only)
- Create Sharing Sets
- Create Sharing Settings (High Volume Community and Portal Users only)
- Clone Profile (for either Customer or Partner Profile) and enable the following:
- Connected App Access--> Conga Composer =
- Administrative Permissions--> API Enabled =
- Custom Object Permissions and Layouts--> Appropriate access to Conga objects for this profile
- Custom Profiles must be used because standard portal/community profiles do not have the ability to send APIs
- Add custom profiles to Community Members selected profiles list
- Enable contact as External User Contact --> Manage External User --> Enable Customer/Partner User. Once on edit page select appropriate profile (remember - custom profile)
- When saving a Salesforce File as a Community user, use the ContentNetworkId parameter to specify the appropriate Network Id for the Community.
- Queries must be used instead of Salesforce Reports for related lists. The first line of the Composer button url should be modified to reflect the Community's domain, as shown in the following example:
To prepend your My Domains URL, like
- If using Files, community users may struggle with access to Conga Templates. Using Attachments and disabling Files is a workaround for this issue
- We always recommend using Conga Trigger in the Community. Reasons for this are:you can set a Sys Admin as the running user of a Salesforce workflow, so a Community user does not need any additional permissions at all. They simply trigger the workflow, and the permissions belonging to the running user of the workflow are then used to trigger Composer.
- There is currently an issue with returning to the record in the Community once a document has been created. ReturnPath currently is not compatible in the Community. Instead, a user may be redirected to the community log in page.