Sorting for Custom and Default Views in Documents Tab

The Documents tab in a contract record preserves sorting preferences for each custom and default view, maintaining consistent sorting when switching tabs or refreshing the screen. Sorting selections remain specific to each view, allowing users to retain their chosen order for documents across sessions and view changes.

Recipient Selection: Automatic Search Field Reset

The recipient selection input field now automatically clears after each selection, allowing users to continue adding recipients without manual cleanup. The dropdown highlights selected options, prevents duplicate selections, and enables removal of recipients using the clear icon. This update applies to the Send for Review page and all related pages where recipient selection is available. For more information, see Simple Review.

Tracking for Conversation Objects in Audit and Access Dashboard

The Audit and Access Dashboard now supports tracking for ConversationThread, ConversationMessage, and ConversationParticipant objects when these are created via API. All fields for these objects are enabled by default in the DataChangeTrackingConfig, allowing administrators to view and select these objects in the Object Name dropdown for audit reporting. For more information, see Audit and Access Dashboard Configuration and Audit and Access Dashboard.

Duplicate File Check for Third-party Paper Upload

The system now performs a duplicate file check when uploading third-party paper documents using Discovery Agent during contract creation with Enhanced Authoring Flow feature. If a duplicate file is detected, a “Document Already Exists” alert is displayed.

This enhancement applies when creating contracts from the My Contracts, All Contracts, and Accounts pages using the Upload Third-Party Paper option with the Use Discovery Agent toggle.

For more information, see Uploading a Third-party Paper (with Enhanced Authoring Flow).

Obligation Fulfilment Notification Reassignment

Obligation fulfillment notifications now automatically reflect reassigned assignees and reviewers. When an obligation fulfillment is edited and reassigned, all future notifications and reminders are sent only to the updated recipients, and previous recipients no longer receive related alerts. For more information, see Obligation Fulfillment.

Consolidated Obligation Notifications on Contract Activation

When a contract is activated, Conga CLM sends a single consolidated email notification to each obligation assignee and reviewer. Each recipient receives one email per contract activation that lists only the obligations assigned to them. For more information, see Auto-activation of Contracts.

Policy-based Access Control for Supplier Group Entity

Conga CLM now supports policy-based access control based on Supplier Group attributes, in addition to the existing Account Group, Contract Group, Legal Entity controls. Administrators can define and manage reusable common attributes on the Supplier Group object and associate them with contracts and master data. These attributes work with existing RBAC permissions to control who can see and act on specific contracts and records, improving data protection while preserving current behavior. Supplier Group field is introduced in the supplier creation page to support this feature.

When determining user authorization for contracts, the system evaluates both object-level and property-level permissions for the Supplier Group object. Configuring both object-level and property-level permissions is optional. If data security requirements require property-level control over CRUD operations, administrators can configure permissions at both levels. If property-level permissions are not configured, authorization behavior remains based solely on object-level permissions. For more information, see Creating a Common Attribute.

Implicit Contract Access for Obligation Assignees and Reviewers

When a contract manager assigns an obligation to a user (assignee or reviewer), if the selected user does not already have access to the contract, the system displays a confirmation prompt. Access is granted only upon confirmation. If the contract manager declines, the obligation assignment proceeds without modifying contract access. This eliminates the need for contract managers or administrators to explicitly assign permissions and enables users to view the contract to effectively complete their obligation fulfillment responsibilities.

For more information, see Creating an Obligation.

Rejected Status for Obligation Fulfillments

When a reviewer rejects an obligation fulfillment, the status now updates to Rejected instead of Not Fulfilled, providing clearer and more consistent tracking of rejected records. For more information, see Obligation Fulfillment Lifecycle and Reviewing an Obligation Fulfillment.

Bulk Edit Field-Level Permission Controls for Clause List View

Restrict access to the Bulk Edit feature in the Clause List View by configuring permission groups and UI rules. Designate specific fields—Clause Name, Source Action, Approval Status, Agreement Type, Approver Comments, Clause Text, Previous Text, Clause Diff Text, and Is Active—as read-only or hidden for Negotiator roles, while allowing managerial roles to access them as needed. UI rules provide an additional layer of control beyond existing role-based access controls, without impacting service hook operations or requiring changes to permission sets. For more information, see Roles and Permissions.