Administrators can pre-approve users to connect via OAuth when running solutions. This method masks the session ID and URL when using Visualforce® buttons, and prevents pop-up authorization requests on mobile devices when running Composer solutions on Salesforce1®.
In addition to configuring Conga Composer® as a Connected App, you will want to 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®.
To configure Conga Composer as a connected app to use OAuth:
Navigate to Setup > Manage Apps > Connected Apps > Conga Composer.
Change the Permitted Users picklist to .
Admins must be pre-approved in the Connected App. If not, you may see an error message when trying to launch a Conga Composer OAuth button.
Designate which users connect to Conga Composer via OAuth by adding Profiles (click) or Permission Sets (click ).
After setting the Permitted Users to be pre-authorized, administrators can add Profiles or Permission Sets in order to specify which users are approved.
Pre-approved users will not see Allow or Deny prompts when accessing Composer via OAuth, and Conga Composer automatically creates a refresh token.
Users who are not part of the defined Profiles or Permission Sets will be denied access.