Go-live

Go-live marks the final step before users begin working in the live environment. This section guides you through the essential setup activities required to make the system operational, including migrating required components from your source environment and adding users with appropriate access. Completing these steps ensures a smooth transition and prepares your organization for day-one usage.

Migrate Components

For Conga PS team, recommendation is to use excel based CLM deployment manager tool developed by Conga PS Innovation team.

For Partners and customers until this tool is available for external use, use the Migration Manager for migrating objects and its fields. Follow steps mentioned below:

In the Source Org.

From Conga Start, click the App Launcher icon ( ) and select Migration Manager.
Click Config/Schema tab and click Create Package.
Select objects for migration and click Next.
Select the configurations you want to include and click Submit.
Provide name for package and click Save.
Download the package.

In the target org.

From Conga Start, click the and select Migration Manager.
Click Config/Schema tab and click Import Package.
Figure 1.
Drag and drop or browse the package to be imported and click Import.
Figure 2.

Migrate custom components using the steps mentioned in Custom Code Deployment.

Add Users

Before creating a user record, it's important to understand types of users that can be created in the Conga Platform. For more information see, User Types.

Once the user type is determined, you can either create a user record manually from the Admin UI or perform bulk import.

Follow the steps mentioned in Add Users to add users manually from Admin UI.

Follow the steps mentioned in Importing User to import users in bulk from valid CSV file.

Follow the steps mention in Auto-Provision Users From External System to automatically create their Advantage Platform accounts when they first log in. It helps administrators simplify user onboarding by removing the need for manual user creation.

User Profiles

A profile contains user permissions and access settings. There are five basic profiles used with Conga CLM:


Profile Name	Available Permissions Description
Conga CLM Administrator	Can configure and customize the application. Has access to all Conga CLM functionality that does not require an additional license.
Contract Manager/Template Admin	Can create, edit, execute, and approve contracts. This profile can also delete contracts as long as they are not executed. Can manage clause and language template library. Has access to X-Author for Contracts functionality
Read Only	Can view the organization's setup, run and export reports, and view, but not edit other records.
Requester/Approver	Can initiate new contract requests and use the Contract Wizard to assemble standard contracts, but does not have access to X-Author for Contracts. Can perform some limited searches and reporting.
Contract Creator/Negotiator	Can create, edit, execute, and approve contracts. This profile cannot delete agreements and does not have any permissions to manage clauses or templates. Has access to X-Author for Contracts in a negotiator role.

CLM user roles & tasks: The following table presents the broad view of some of the key CLM roles and their descriptions:


Role	Description
Legal function	Design, creation, maintenance of contract template contents Review, negotiation, and contract legal content assurance Legal admin, Internal counsel, External counsel
Finance function	Evaluation and validation of contract’s financial impact and risks Approval of the commitment of resources per the contract Financial analyst, Controller, CFO, Treasurer
SMEs	Evaluation and validation of specific areas of contract commitments Approval of their functional area of the contract’s deliverables VP / Director for Products, Procurement, Sales, Partner Management
Contract Facilitator	Definition of non-standard, complex, or global contract components Assignment of contributors, scoring, approval, and strategic aspects VP Strategic Accounts, CEO, CFO, COO
Admin	General definition of process, contributors, contract elements Configuration of applications and tools required by the process Application admin, system analyst, business analyst

Creating a user profile

Profile is essentially a definition of a set of permissions granted to a group of users.
Adding a single user
The maximum number of users you can create is determined by the idenSalesforce Edition.
Adding multiple users
The maximum number of users you can create is determined by your Salesforce Edition. Depending on the number of available licenses, you can create up to 10 users.
Assigning Conga CLM license to a user
In addition to Salesforce licensing, a user profile must be assigned to the Conga CLM license.
Assigning users to queues
Queues allow groups of users to manage a shared workload more effectively. A queue is a location where records can be routed to await processing by a group member. If the sharing model for all objects in the queue is Public Read/Write/Transfer, you do not need to assign users to the queue, as all users already have access to the records for those objects.
Providing read access
This allows preview and generate agreement actions to read the document password from the Admin object without allowing them to view it. You can set the permissions and page layouts for the selected profile. The permissions defined here control access at the object level. Set access levels based on the functional requirements for the profile. For example, create different groups of permissions for individual contributors, managers, and administrators.

Roles and Permission Groups

Role and Permission Group management helps administrators configure security on the Conga Platform for CLM users. A role represents a profile (for example, system admin, contract facilitator, general user, and so on). Administrators can create user roles that contain a set of permissions with specific access to objects, records, pages, and administrative functions in applications built on the Conga Platform. You can use the User Interface or REST APIs per your business needs. You can add permission group of the user in Admin Console. > Users

The following are covered in role and permission group management.

Role-Based Access Control (RBAC) for Users: Conga supports RBAC to grant or restrict access to various applications and data within the Conga Revenue Lifecycle Platform. Conga RBAC supports data access primarily through mechanisms such as object permissions, permission groups, roles, and so on. You can create roles to restrict access to data for certain users based on their functional roles and responsibilities. For instance, if a user is assigned the CongaCLMReadOnlyUser role and navigates to the Contact page, certain options such as Create Contact, Edit, Delete, or Create Contract on the Details page are not displayed for that user.
Roles: Roles determine a user's access to applications, objects, records, and permissions to perform actions on the Conga Advantage Platform. A role is assigned to users performing similar tasks and consists of a set of permissions. You can assign roles to the existing users or create a new user and edit the user details to assign roles. For example, Contracts Facilitator, Contract Manager, and so on.
User Groups: User groups enable you to create groups of individual users with specific roles and permissions. You must add the permission group of the user in Admin Console > User Management.
Permission Groups: A permission group is a group of object permissions. Permission groups can be assigned to individual users or roles. You can also assign multiple permissions and permission groups to a user to grant access to all the assigned role permissions. For example, with the CongaCLMReadOnlyUser role, a user can view all records they have permission to see when navigating to the Search tab on the Contract Details page.

The following table maps the standard roles to their respective permission groups for supplier management:


Roles	Associated Permission Groups
Business User	Conga Business User Permission Group
Supplier Manager	Conga Supplier Manager Permission Group Conga Supplier Approver Permission Group (Approver of a supplier) Conga Supplier Request Approver Permission Group (Approver of a supplier request)
Supplier Admin	Conga Supplier Admin Permission Group Conga Supplier Approver Permission Group (Approver of a Supplier) Conga Supplier Request Approver Permission Group (Approver of a supplier request)

For more information, see Roles and Permission Groups topic in Advantage Platform Administration administrators guide.

Object Permissions

Object permissions define the level of access or restriction a user has to a specific object. These permissions are usually granted through permission groups. The Modify All and View All permissions grant users access to all records of an object.

Note: There is no need to control the parent object (Agreement) and child objects (for example, AgreementLineItem) separately with different conditions. It is recommended to manage user access on the Agreement object. By enabling the ViewAll permission for all other CLM objects (like AgreementLineItem), you ensure that the users can view all records of these objects without needing specific access controls for each one. OwnerScope must be enabled exclusively for the Agreement object, with no need to enable it for any other objects.

A user with admin rights can perform all actions. When a new user or tenant is onboarded, you can assign View All or Is Allow Owner Scope permission which need to be enabled in the Schema manager at the object level. Is Allow Owner Scope is a one-time activity and cannot be modified. View All provides access to all records in the organization and Is Allow Owner Scope restricts access to owners.

A few examples of granting permissions for users are:

Granting ModifyAll or ViewAll permissions on the Account or Contact object enables users to view or edit all records in the Account list page or Contact list page. To allow users to create, update, and delete records without needing Modify All or View All permissions, you can assign CRUD (Create, Read, Update, and Delete) permissions independently.

Granting ViewAll permissions on the Menu object allows users to view the following submenus.


Menu	Submenus
Contracts	My Contracts All Contracts Recently Viewed Search
Accounts	My Accounts Recently Viewed All Accounts
Contacts	My Contacts Recently Viewed All Contacts
CLM Admin Setup	General Settings Document Format Setup Document Protection Setup Document Versioning Contract Action Settings PDF Security Settings X-Author Configuration Settings Bulk Import Contract Rules CLM Feature Management Spend Category Supplier Management Settings Team Role
Clause Library	NA

The following table lists the permission levels that can be assigned to a CLM user on various objects.


Object	Read	Create	Update	Delete
Agreement	Displays the My Contracts, Recently Viewed, and Search tabs in the LINKS panel.	Create new contract records from My Contracts or Recently Viewed tabs. Create a new contract record from the account details page	Edit a contract record. Bulk edit contract records	Delete a contract record using the kebab menu or custom actions. Bulk delete contract records Delete a contract associated with an account or a contact.
AgreementLineItem	Displays the Line Items tab in the LINKS panel.	Add a new line item for a contract record. Clone a line item for a contract record.	Edit a contract record's line item.	Delete a contract's line item.
ContractRequest	Displays the My Requests, All Requests, and Incoming Requests sub-menus in the Manage Requests menu	Create a new contract request	Edit a contract request	NA
AgreementClause	Displays the Clauses tab in the LINKS panel.	Create a new clause record. Clone a clause record on the Clause Details page.	Edit a clause record.	Delete a clause on the Clause Details page.
DocumentMetadata, Configuration	Displays the following: Documents tab in the LINKS panel depends on DocumentMetadata. Bulk Import in the CLM Admin depends on DocumentMetadata and Configuration. Template tab depends on Configuration.	Upload a document	NA	Delete a document using the kebab menu.
RelatedAgreement	Displays the Related Contracts and Relationships tabs in the LINKS panel.	Create a new relationship with other contracts.	NA	Delete a related agreement. Remove a relationship type with other contracts by selecting the Unlink icon () in the Actions column.
AgreementInsight	Displays the Insights tab in the LINKS panel.	NA	NA	NA
RelatedItems	Displays the Related Items tab in the LINKS panel	Add objects and their records linked to a contract.	Edit objects and their records linked to a contract.	Delete objects and their records linked to a contract.
Account	Displays the Accounts List page in Accounts Apps	Create a new account.	Edit an account.	Delete an account.
Contact	Displays the Contact List page in Contact Apps.	Create a new contact.	Edit a contact.	Delete an existing contact. Delete a contact associated with an account.
AgreementObligation	Displays the Obligation List page in Contract Apps.	Create a new obligation.	Edit an obligation.	Delete an existing obligation.
AgreementObligationFulfillment	Displays the list of contracts for obligation fulfillmentList in Obligation Fulfillment page	NA	Edit an obligation in fulfillment	NA
SupplierRequest	Displays the list of supplier requests	Create a supplier request	Edit a supplier request	NA
Supplier	Displays the list of suppliers	Create a supplier	Edit a supplier	Delete a supplier
Configuration	Displays the following sub-menus in CLM Admin Setup. General Settings Document Versioning Contract Action Settings PDF Security Settings X-Author Configuration Settings Bulk Import CLM Feature Management Supplier Management Settings	NA	Updates the fields in each of the following sub-menus under CLM Admin Setup. General Settings Document Versioning Contract Action Settings PDF Security Settings X-Author Configuration Settings Bulk Import CLM Feature Management Supplier Management Settings	NA
DocumentOutputFormat	Displays the Document Format Setup for contract documents.	Create the contract document formats at the User Role and Contract Type levels.	Update the contract document formats at the User Role and Contract Type levels.	Delete the contract document formats at the User Role and Contract Type levels.
AgreementProtection	Displays the Document Protection Setup for contract documents.	Create the agreement protection setup to contract documents for specific roles by making the documents read-only.	Update the agreement protection setup to contract documents.	Delete the agreement protection setup to contract documents.
AgreementRule	Displays the Contract Rules for contract documents.	Create new contract rules in New Rule menu.	Edit the contract rules in Details and Rule Configuration.	Delete the contract rules.
TeamRole	Displays the Team Role in CLM Admin Setup.	Add team role in Add New Team RoleTeam. Schema changes to be made.	Edit the Team Role.	Delete the team role using the kebab icon which also requires ContractTeamMembers Read permission.
SpendCategory	Displays the Spend Category.	Add category details in Add Category. Schema Manger filed to be selected.	Edit the Spend Category using the kebab icon.	Delete Spend Category using the kebab icon.
Clause Library-Template	Displays TemplateVersionDynamicSection.	Create new clause using New Clause. For New Clause or Clone following permissions are needed: Template - CREATE Template - UPDATE (always required) TemplateVersion - CREATE TemplateVersion - READ DocumentMetadata - CREATE TemplateVersionClauseReference - READ TemplateLocale - READ Template - ViewAll TemplateVersion - ViewAll	Edit the clause with the following permissions: Template - UPDATE TemplateVersion - CREATE TemplateVersion - READ DocumentMetadata - CREATE TemplateVersionClauseReference - READ TemplateLocale - READ Template - ViewAll TemplateVersion - ViewAll	For Standard Clauses or Web Clauses, following permissions are needed: Template - DELETE TemplateVersion - DELETE TemplateVersionClauseReference - DELETE TemplateVersionDynamicSection - READ TemplateVersionDynamicSection - DELETE For Alternate Clauses: Template - DELETE TemplateVersion - DELETE TemplateVersionClauseReference - DELETE TemplateVersionDynamicSection - READ TemplateVersionDynamicSection - DELETE AlternateClauseMapping - READ (ADDITIONAL)
Clause Library - AlternateClauseMapping, ClauseConfiguration	Displays AlternateClauseMapping.	AlternateClause tab requires the following: AlternateClauseMapping - CREATE AlternateClauseMapping - READ ClauseConfiguration - CREATE	NA	NA
Clause Library -Obligation	Displays Obligation.	Clause Library -Obligation requires the following permissions: Obligation - CREATE ClauseObligation - CREATE ActivityHistory - CREATE	Update the following permissions: Obligation - UPDATE ClauseObligation - UPDATE	Delete the following: Obligation - DELETE ClauseObligation - DELETE
To work with entire clauselibrary along with ViewAll permission on Template and TemplateVersion objects, the following permissions are needed:
Template	CREATE	READ	UPDATE	DELETE
TemplateVersion	CREATE	READ	NA	DELETE
TemplateVersionClauseReference	NA	READ	NA	DELETE
TemplateVersionDynamicSection	NA	READ	NA	DELETE
DocumentMetadata	CREATE	NA	NA	NA
TemplateLocale	NA	READ	NA	NA
AlternateClauseMapping	CREATE	READ	NA	NA
ClauseConfiguration	CREATE	NA	NA	NA
Obligation	CREATE	READ	UPDATE	DELETE
ClauseObligation	CREATE	NA	UPDATE	DELETE
ActivityHistory	CREATE	NA	NA	NA

Record Type Permissions

Record Type permissions is managed through Permission Groups > Object Permissions. By default, all record types within an object are accessible to all users who have access to the object.

A record type permission allows administrators to define and enforce these permissions at the record type level for different user roles, as needed. This ensures that users have access to specific record types when creating records. For instance, if an Agreement or ContractRequest object contains two record types, Non-Disclosure Agreement (NDA) and Master Services Agreement (MSA), an administrator can configure the system so that:

All users can create records using the NDA record type.
Only users with specific roles (for example, legal team or contract managers) can create records using the MSA record type.

Action Permissions

In addition to the standard CRUD operations, you can assign custom object-specific actions that can be set for CLM users. The following table lists a few of the action permissions (for example, such as Clone, Share, and so on)


Object	Action Permissions	Functionality
Agreement	Clone	To clone a contract record.
	Share	To share a record with any user or user group.
	Preview & Submit	To display the Preview & Submit button under Approvals.
	My Approvals	To display the My Approvals button under Approvals.
	Co-Pilot	To grant a user access to Q&A Agent.
	Redline AI	To grant a user access to Redline AI.
	Change Owner	To allow users to reassign ownership of a contract record to a user, user group, or to themselves.
	Adobe Sign Tracking	To display Adobe Sign icon in the contract's right panel to track Adobe Sign related audit trail.
ActivityHistory	ViewCLMActionPanel	To display the Activity option in the right panel on the Contract Details page.
ReviewCycle	ViewCLMActionPanel	To display the Review Cycle option in the right panel on the Contract Details page.
ContractRequest	Cancel Request	Allows the requester to cancel a contract request listed in My Requests or All Requests sub-menus.
	Submit for Approval	Allows the requester to submit a contract request for approval.
	Approve & Reject	Allows an approver to approve or reject a contract request from the Incoming Requests sub-menu.
	Withdraw	Allows the requester to withdraw a submitted contract request listed in My Requests or All Requests sub-menu and return it to Draft status.
AgreementObligationFulfillment	Edit Fulfillment	To edit obligation fulfillment after activation.
SupplierRequest	Submit \Supplier Request for ApprovaL	Allows the Supplier Manager, Supplier Admin, Business User to submit a supplier request.
	Approve Supplier Request	Allows the Supplier Manager, Supplier Admin to approve a supplier request.
	Reject Supplier Request	Allows the Supplier Manager, Supplier Admin to reject a supplier request.
	Withdraw Supplier Request	Allows the Business User (creator/requester/owner), Supplier Admin to withdraw a supplier request.
	Cancel Supplier Request	Allows the Business User (creator/requester/owner), Supplier Admin to cancel a supplier request.
	Create	Allows the Business User (creator/requester/owner), Supplier Admin to create a supplier request.
	Convert to supplier	Allows the Supplier Manager, Supplier Admin to convert to a supplier.
	Approve & Convert to Supplier	Allows the Supplier Manager, Supplier Admin to approve and convert to a supplier request.
	Change Supplier Request Manager(s)	Allows the Supplier Admin or authorized users to update the Supplier Manager user group assigned to a supplier request.
Supplier	Create	Allows the Supplier Admin or authorized approver to create a supplier.
	Submit Supplier for Approval	Allows the Supplier Admin or authorized approver to submit a supplier record for approval.
	Approve Supplier	Allows the Supplier Admin or authorized approver to approve a supplier.
	Delete	Allows the Supplier Admin or authorized user to delete a supplier record in Draft status.
	Reject Supplier	Allows the Supplier Admin or authorized approver to reject a supplier.
	Withdraw Supplier	Allows the Supplier Manager or authorized user to withdraw a supplier.
	Inactivate	Allows the Supplier Manager or authorized user to deactivate a supplier.
	Change Owner	Allows Supplier Managers or authorized users to change the owner of a supplier record.

Field Permissions

In addition to the object permission, you can define and enforce access permissions at the field level for different user roles. The following table lists some of the field-level permissions (for example, RecordOwner, RecordType, and so on) that can be set on Agreement or ContractRequest object for users.


Object	Field Permissions	Read	Edit
Agreement	RecordOwner	View the Owner field on the Contract Details page but cannot edit.	Modify the Owner field on the Contract Details page.
Agreement	RecordType	View the Contract Type field on the Contract Details page but cannot edit.	Modify the Contract Type field on the Contract Details page.
ContractRequest	Requester	View the Requester field in the My Requests > Parties but cannot edit.	Modify the Requester field in the My Requests > Parties.
ContractRequest	Owner	View the Owner field in the My Requests > Parties section but cannot edit.	Modify the Owner field in the My Requests > Parties section.

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.