To connect a user to Conga Sign servers, the user must have a License assigned, and have the Profile level permission of a System Administrator.

Necessary Permissions:

• Modify All Data

  • This permission is required to verify administrator privileges during the initial setup process. It ensures that only authorized users with appropriate system-level access can complete the Conga Sign configuration.

• Access to Metadata API

  • The setup wizard needs this permission to create custom fields and configure the necessary permission sets for Conga Sign functionality. This allows the automated setup process to properly configure your Salesforce environment for seamless integration.

• Customize Application

  • This permission enables access to protected custom settings where Conga Sign securely stores your connection keys. These encrypted credentials are essential for maintaining the secure connection between Conga Sign and your Salesforce instance.

Additional Permissions Required:

• Read access to objects used with (for example, Opportunity)
• Read/Write access to Conga Sign Transaction [APXT_CongaSign__Transaction__c] and all fields
  • Including any setup generated lookup fields (e.g Opportunity [Parent_006__c])
• Read/Write access to Conga Sign Document [APXT_CongaSign_Document_c] and all fields
• Read/Write access to Conga Sign Recipient [APXT_CongaSign__Recipient__c] and all fields
• Permission to Apex Classes: APXT_CongaSign__apxt_setup
• Permission to VF pages: APXT_CongaSign__apxt_setup
• Permission on the User Record: Salesforce CRM Content User is enabled
• Profile Permission → Administrative Permissions → Manage Salesforce CRM Content is enabled

• Package License granted
• Read access to objects used with (for example, Opportunity)
• Read access to Conga Sign Transaction [APXT_CongaSign__Transaction__c] and all fields
  • Including any setup generated lookup fields (e.g Opportunity [Parent_006__c])
    Note:

    To allow non-admin users to cancel Conga Sign Transactions that they are not the record owner of, you must provide them both Read and Edit Access to the Conga Sign Transaction object

• Read/Write access to Conga Sign Document [APXT_CongaSign_Document_c] and all fields
• Read access to Conga Sign Recipient [APXT_CongaSign__Recipient__c] and all fields

• APXT_CongaSign__apxt_cancelTransaction
• APXT_CongaSign__apxt_contentInfo
• APXT_CongaSign__apxt_coretransactionservice
• APXT_CongaSign__apxt_resendTransaction
• APXT_CongaSign__apxt_sendForSignature
• APXT_CongaSign__apxt_serviceRedirect
• APXT_CongaSign__apxt_setup
• APXT_CongaSign__apxt_conga_sign.apxt_transactionlinkcontentdoc
• APXT_CongaSign__apxt_conga_sign.apxt_transactionlinksrcobject

• APXT_CongaSign__apxt_auditTransaction
• APXT_CongaSign__apxt_cancelTransaction
• APXT_CongaSign__apxt_contentInfo
• APXT_CongaSign__apxt_editTransaction
• APXT_CongaSign__apxt_resendTransaction
• APXT_CongaSign__apxt_sendForSignature
• APXT_CongaSign__apxt_serviceRedirect
• APXT_CongaSign__apxt_setup

• Salesforce CRM Content User is enabled
• Profile Permission → Administrative Permissions
  • Manage Salesforce CRM Content is enabled