Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Page Sections

Configure the Conga Composer Connected App

Administrators can pre-approve users to connect via OAuth when running Composer solutions. This method masks the session ID and URL when using Visualforce buttons, and prevents authorization requests when using Composer OAuth buttons, and prevents pop-up authorization requests on mobile devices when running Composer solutions on Salesforce Mobile.

Note:

In addition to configuring Conga Composer as a Connected App, create Conga Composer OAuth buttons (or update existing non-OAuth buttons) to launch your Composer solutions. This is not required in Salesforce Classic, but it is required in Salesforce Lightning.

Configure Conga Composer App for OAuth

  1. Navigate to Salesforce Setup
  2. Go to Manage Connected Apps.
  3. Click Edit next to the appropriate connected app for your region. It will be listed as the following, depending on your region and if you are using Standard Composer solutions or integrating with Conga for Advantage Platform:
    Region and FunctionalityConnected App Names
    Standard Composer merging, North America, Europe or Australia regions
    • Composer NA for Salesforce
    • Composer EU for Salesforce
    • Composer AP for Salesforce
    Standard Composer merging, using PlatformComposer=1 or using Document Merge UI
    • Conga Platform - Composer NA
    • Conga Platform - Composer EU
    • Conga Platform - Composer AP
    Composer Lightning ComponentComposer Lightning for Salesforce
    Composer Lightning Component, using PlatformComposer=1 or using Document Merge UIComposer Platform - Composer Lightning
    1. If you are using Composer and Sign integration, refer to the Composer for Advantage Platform documentation, Composer & Sign Connected App Scopes.
  4. Change the Permitted Users picklist to Admin approved users are pre-authorized.
  5. Click Ok to accept the security warning.
  6. Change the IP Relaxation dropdown to Relax IP Restrictions. If IPs must remain enforced, whitelist the Composer IP addresses: Add Conga Composer IP Addresses.
  7. Click Save.
  8. Open the Composer connected app by clicking Conga Composer.
  9. Scroll down to the Profiles section, click Manage Profiles, and add all the Profiles that will be using Composer.
    Note:

    Admins must be pre-approved in the Connected App. If not, you may encounter the following error messages when trying to launch a Conga Composer OAuth button:

    "There was an error processing your request.", "You are not authenticated to perform this action."

    Pre-approved users will not see Allow or Deny prompts when accessing Composer via OAuth, and Composer automatically creates a refresh token.

    Users who are not part of the defined Profiles of Permission Sets will be denied access.

Verify Your Connected App Region

To verify which region-specific connected app is configured in the Salesforce org:
  1. Log into Salesforce as System Administrator
  2. Go to Salesforce Setup
  3. Navigate to Custom Metadata Types
  4. Under Composer Setting, Click Manage Records
  5. Click Settings
  6. Under the Connected App Setting field: Click the Connected App Setting value
    1. Connected App Name: Name of the Connected App used for standard Composer merges (non-Platform)
    2. Connected App Name (Platform): Name of the Connected App used for standard Composer merges (using PlatformComposer=1 parameter)

You are able to verify which region your Composer Connected Apps uses for merging.