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 you to 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). You 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.

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 you 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), you 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.

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.