home

Composer for Salesforce

Adobe Sign ServicesAiMeAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for Excel for SalesforceX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release
Adobe Sign ServicesAiMeAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)CPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for Excel for SalesforceX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneralDocs by Release

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 Contents

Composer for Salesforce

Conga Composer Implementation Guide

Initial Platform Setup

Here, we cover creating and configuring users, understanding roles and permissions, and configuring Composer Settings to shape the experience for your organization. If you are also connecting Salesforce to Composer, complete this section first, then proceed to Salesforce Connector Setup.

How authentication works

Users log in to the Platform using an Identity Provider (IDP). For most Composer users, this will be either:

  • Salesforce IDP - the user authenticates with their Salesforce credentials. The Platform maps them to their Platform account using their Salesforce User ID (External ID).

  • Conga IDP - the user authenticates directly with Conga using a username and password. The Platform sends them a welcome email with login credentials on account creation.

The IDP you use determines what goes in the External ID field and how the user logs in.

User Types

When creating a user, the User Type field determines the nature of their account. For Conga Composer, you will primarily work with two types:
User TypeWhen to Use
Internal Standard users who are employees or members of your organization. This is the correct type for anyone who will be sending or managing Sign transactions.
Integration System accounts created specifically for API connections or automated data sync between systems. Use this type for the dedicated Salesforce connector user.
Warning: When an Integration user is saved, the Platform generates a Client ID and Client Secret for that account. Copy both values immediately - the Client Secret cannot be recovered after you navigate away from the page. There is no way to retrieve it; you would need to regenerate credentials entirely.

Creating a User

Navigate to Admin Console → Users and click Add to open the User Details form.

Required Fields

FieldDescription
User TypeSelect Internal for standard Composer users, or Integration for the connector user.
First NameThe user's first name.
Last NameThe user's last name.
EmailThe user's email address. For Conga IDP users, this is also what they use to log in. If multiple accounts share the same email address, the most recently created account becomes the primary.
UsernameFor Conga IDP users: auto-populated from the Email field. Can be customized to create an email alias (e.g., [email protected]) if multiple accounts share the same email. For Salesforce IDP and other external IDP users: enter a username for informational purposes only - it is not used for authentication.
RoleThe role controlling the user's permissions on the Platform.
External IDMaps the user to an external system for data sync and authentication. For Salesforce IDP users: enter the user's Salesforce User ID. For Conga IDP users: enter any unique identifier.
Optional Fields
FieldsDescription
Permission GroupsAdditional permission groups beyond what the assigned role provides.
Organization External IDThe IDP connection to associate this user with. Defaults to your organization's default IDP. Only change this if the user should authenticate through a different IDP than your default.
TimezoneThe user's timezone. If left blank, the organization's timezone is used. Affects transaction expiration date calculations.
Preferred LocaleThe user's locale for formatting dates, numbers, and currency. If left blank, the organization's locale is used. Only displays locales enabled at the organization level.
CurrencyThe user's default currency. If left blank, the organization's currency is used.
AliasA short display name for the user.
LanguageThe user's language code (e.g., en-US).
AddressThe user's address.
Phone NumberThe user's phone number.

October 8, 2026