Document Group Support in Document Creation APIs

Conga CLM now supports policy-based access control based on Document Group attributes. Administrators can define and manage reusable common attributes on the Document 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.

To support policy-based access control based document group, a new field ‘Document Group’ is included in document metadata for the following API endpoints:

/api/clm/v1/contracts/{contractId}/documents

/api/clm/v1/contracts/{contractId}/documents/large

/api/clm/v1/sign/esignatures/wetsign/{transactionId}/end

/api/clm/v1/contracts/createoffline/large

/api/clm/v1/contracts/storeexecuted/large

/api/clm/v1/contracts/{contractId}/importoffline/large

/api/clm/v1/contracts/{contractId}/supportingdocument

/api/clm/v1/contracts/{contractId}/generate

/api/clm/v1/contracts/{contractId}/regenerate

API responses now return the document group value as part of the document metadata, supporting improved document classification and management.

Action-Level Permissions for Left Navigation Menus on Contracts

Administrators can now configure action-level permissions for each left navigation menu on the Contract record using role-based access control, allowing precise control over menu visibility and access per role. Menu items, including standard and custom entries are hidden from users and inaccessible via the API when permissions are disabled, with all changes logged for auditability. For more information, see Hiding Navigation Menus on the Contract Record.

Search in Global Documents for Conversation Attachments

Search for global documents by name when attaching documents under Conversations using a search bar that appears after entering at least two characters. For more information, see Creating a Post, Editing a Post, and Replying to a Post in the Application.

Single Save as Draft Option for Multi-Contract Requests

The multi-contract request screen now displays only one Save as Draft option, removing redundant actions and aligning with the single-contract request experience. All entered data across contracts is saved in a single draft.

Sorting of Common Attributes in Grouped Layouts

Common attributes within Contract Group, Account Group, Supplier Group, and Legal Entity Group now display in alphabetical order by default on their respective record layouts. Sorting is case-insensitive and applies to the attribute display label, providing a consistent and predictable experience across all supported objects.

Global Document Management for Accounts

Contract users with appropriate permissions can upload and manage global documents for the Accounts object, making these documents accessible across all Account records via Conga Drive.

The Files section in the Account Details includes Global Documents tab in addition to the Other Documents tab. You can upload file up to 10 files, with a combined size limit of 25MB. You can also download and delete files associated to an account. For more information, see Uploading a Document to the Repository and Managing Account's Files

Policy-based Access Control for Document Group Entity

Conga CLM now supports policy-based access control based on Document Group attributes. Administrators can define and manage reusable common attributes on the Document 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. Document Group field is introduced in the Documents tab in the contract details page to support this feature.

When determining user authorization for contract documents, the system evaluates both object-level and property-level permissions for the Document 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 and Uploading a Document.

Custom Lifecycle Logic Using Callbacks

Administrators can now implement custom code for the Generate and Activate lifecycle actions using callbacks. This enables advanced business logic to be executed before the action proceeds. For example, you can implement custom validations to verify that required fields are populated and prevent the action from executing until the defined criteria are met. For more information, see Callback Methods for Agreement Object.

Document Visibility Setting

Administrators can configure the document group attributes and defaults. They must enable and configure Property-based Access Control (PBAC) for all permission groups assigned to a user to enforce document security restrictions. If PBAC is not configured for all groups, users may retain broader access through other permission groups. For more information, see Creating a Common Attribute.

Users can now set a document group when uploading, generating, importing, or sending contract documents for signatures. The document group controls which users can access the document, allowing sensitive documents to be restricted to the appropriate audience from the point of upload. For more information, see Generating a Contract Document, Regenerating a Contract Document, Generating a Supporting Document, Uploading a Document, Uploading a Signed Document, Uploading a Third-party Paper, Importing an Executed Contract, Importing Contract Details from a Third-party Document, Importing an Executed Contract with Enhanced Authoring Flow, and Importing Offline Documents.

Users can also update the document group for an existing document directly from the Documents list without opening the document. For more information, see Editing the Document Group of a Contract Document.

Contract Editing: Disable Actions Panel and Top-Bar Controls

When editing a contract, the system disables all actions in the NEXT STEPS panel and the top bar, including the Share button and the kebab menu, to prevent conflicting actions on unsaved data. Disabled controls are visually distinct and non-interactive. The Save and Cancel buttons remain available. All controls are restored to their normal state after saving or canceling changes. For more information, see Editing One or More Contracts and Availability of Contract Actions.

Seeded Unilateral NDA Staged Workflow

A staged workflow named Unilateral NDA Staged is now automatically seeded for contracts with Contract Type set to NDA and Contract Subtype set to Unilateral. This workflow assembles document generation and email notification stages in sequence, activating automatically upon contract creation without requiring manual configuration by administrators.

Criteria Component for Rule-Based Configuration

The Criteria component enables administrators to define rule-based conditions for assigning Contract Managers to contract requests using configurable field, operator, and value structures. This component supports multiple criteria, logical connectors (AND/OR), nested grouping, and adapts input options based on field types, providing a consistent and flexible no-code rule configuration experience. Existing free-text criteria are automatically migrated and rendered in the builder for seamless transition. For more information, see Contract Request Settings.

Large Document Support for Contract Lifecycle via API

Users can now complete the contract lifecycle for large documents, up to 100MB for .docx files and up to 500MB for .pdf and other file types, using the offline import and store executed APIs. This update enables uploading, storing, and managing large contract documents throughout all contract lifecycle stages.

Standardized Risk Category Values and Undefined State Handling

The Risk Category field now supports five standardized values: ‘High Risk’, ‘Medium Risk’, ‘Low Risk’, ‘No Risk, and ‘Undefined’. When no risk item is defined for a rule, the field displays ‘Undefined’ to clearly distinguish unassessed risk from 'No Risk’. All user interfaces and API responses consistently reflect these values, and existing records are updated to align with the new standard. For more information, see Risk Tiers and Rules Library.