Improved Performance for the All Conversations View

The All Conversations view has been optimized to improve performance. It displays only conversations you started or participate in. Conversations on records you own or created are excluded unless you are also the conversation initiator or a participant.

Supplier Portal Activity History: Filtered View for Supplier Contacts

The Activity History tab and Recent Activity dashboard card in the supplier portal now display only activity performed by supplier contacts from the same supplier organization as the logged-in user. Internal CLM user activity and entries without a recorded author are excluded from these views, ensuring supplier contacts see only relevant actions by their own team. Internal users accessing activity history from buyer-side CLM screens retain full visibility of all activity. For more information, see Supplier Portal.

Admin Setup Page for Action Pre-Validation and Status Mapping

Administrators can now configure pre-validation and status mapping for both standard and custom contract lifecycle actions using a dedicated setup page, with support for default and contract-type-specific overrides. The API endpoints, POST, GET, PUT, and DELETE at /api/clm/v1/settings/lifecycle-action-config, enable creation, viewing, updating (including action label), and deletion of lifecycle action configurations, while enforcing validation against Agreement picklists and permission requirements. Default and non-configurable actions remain read-only, and all changes are validated to prevent incomplete or invalid configurations. For more information, Conga Developer Portal.

Reviewer Response and Comments Visibility in Review Cycle

Users can now view reviewer responses received via email and comments entered directly in the application through the Reviewer Response / Comments column on the Review Cycle screen. Click View to access each reviewer’s response and comment history, including closing comments entered by the contract manager on the reviewer’s behalf. The history displays the latest entry first, with contract manager comments distinctly identified. This update applies across all review types and scopes, while maintaining existing behavior for reviewers with a single comment. For more information, see Viewing Review Cycle Details (Modern UI), Finishing an Individual Review (Modern UI), Finishing All Reviews and Reconciling (Modern UI), and Capturing Reviewer's Response.

The Review Cycle pane now supports legacy reviews initiated before the updated experience, allowing contract owners and legal users to view, track, and act on in-flight reviews without interruption. Legacy reviews display in the new layout with mapped details, enable actions such as finishing or canceling reviews, and present a unified history that interleaves legacy and new cycles for the same agreement. Mixed-state coexistence is supported, ensuring both legacy and new review cycles remain independently actionable and visible in the tracking pane.

A scheduled job migrates existing legacy review data to the new format daily at a predefined time based on the tenant's time zone. The job runs for approximately 10–15 minutes and executes only when the new review experience is enabled. For more information, see Sending a Contract for Review and Sending a Contract for Review (Modern UI).

Migration from Staged Workflows to Lifecycle Workflows for Contract Lifecycle Management

Organizations using out-of-the-box (OOTB) staged workflows for contract stage tracking are automatically migrated to the default Lifecycle workflow during the release upgrade, eliminating legacy staged workflow usage and reducing excessive API traffic from repeated Get Stages API calls. Only the Lifecycle workflow is published and visible for in-flight contracts, with no change to functional stage tracking behavior. This update reduces workflow API traffic spikes and maintains consistent contract workflow management to support platform scalability and stability.

From this release onward, the default OOTB staged flow for Contracts will be unpublished, and the Lifecycle flow will be published automatically. This happens automatically when a customer's tenant undergoes the schema upgrade after the release, and no manual action is required. Impact is limited only to tenants using the OOTB staged flow for Contracts. Tenants using custom staged flows are not impacted. For all in-flight, OOTB staged flow will be automatically handled with Lifecycle workflow, without impacting existing flow.

This enables scalable customer growth by moving from the legacy staged workflow model to the lightweight, Lifecycle workflow. For more information, see Migration from Staged to Lifecycle Workflow.

Add Documents from Related Contracts to Review

Users can now view a Related tab in the Add Documents step, allowing contract owners and reviewers to select documents from parent and sibling contracts within the same family, in addition to the current contract to send for review. The Related tab appears only when related contracts exist and displays only documents the user has read access to, with search option. Selections from both Current and Related tabs are combined in a single summary, and confirming the selection adds all chosen documents to the review. For more information, see Sending a Contract for Review (Modern UI).

Custom Action Button Iframe Rendering in Contract Details

Users can now configure a Custom Action button in the Next Steps section of the Contract Details page to open a specified URL within an embedded iframe, maintaining the user experience within the application. The iframe displays the configured URL without navigating away from the Contract Details screen, and users can return to the original view using back navigation.

Exclude Completed Recurring Obligations from Amendment

Recurring obligations with all fulfilment records in a final status are now excluded when creating an amendment, preventing completed or inactive obligations from being carried forward to the amended contract. This update applies to all terminal statuses for fulfilment records. For more information, see Recurring Obligations.

Supplier Portal Enhancements for Contracts and Obligations

Administrators can now configure the visibility of individual Company Profile tabs for supplier contacts in the supplier portal using a new tab visibility section under CLM Settings > Supplier Portal. Hiding a tab removes it from the supplier portal view without affecting the underlying data, and related action items or dashboard tiles are also hidden for the supplier. The Basic Details tab remains always visible and is not configurable. For more information, see Configuring Supplier Portal Tab Visibility.

The Supplier Portal dashboard provides an overview of contracts, recent portal activity, business classification documents expiring within 60 days, and obligations due within 30 days. Supplier contacts can select dashboard tiles to access the corresponding lists or Activity History, helping them monitor upcoming commitments and their organization’s portal activity.

Supplier contacts can view contracts linked to their organization from the Contracts tab in their Company Profile. The read-only list displays key contract and document information and supports search, sorting, advanced filters, and saved views. Users can preview and download contract documents, subject to document-group visibility permissions. Role-based access restricts supplier contacts to authorized data and actions within their organization, helping protect sensitive information.

Supplier contacts can view obligations assigned to their organization across contracts, access obligation-related information from the fulfilment details page, and submit fulfilments to meet contractual commitments. The Obligations tab in the Supplier Portal and supplier profile displays assignee and reviewer information in the fulfilment list and detail views, helping users identify the individuals or groups responsible for each fulfilment. For more information, see Supplier Portal.

CLM Quickstart: End-to-End GTM Business Flows with OOTB Roles

The CLM Quickstart package supports end-to-end execution of three core GTM business flows—Self Service (NDA), Legal Assist with Approvals (MSA), and Supplier Contract (Purchase Agreement)—using only out-of-the-box seeded roles, with no custom roles or manual post-install configuration required. For auto-activation in Self Service (NDA) and Supplier Contract (Purchase Agreement) flows, contracts must have "Agreement Start Date" on or before today, "Term Type" set to Fixed Term, and "Status/Status Category" as In Signatures or Fully Signed; for Legal Assist with Approvals (MSA), contracts must have "Total Contract Value" greater than 100,000 and a populated "Sponsor" field to trigger the approval process. For contracts created from Third Party Paper with Discovery AI extraction in the Legal Assist with Approvals (MSA) flow, enable "Enhanced Authoring Flow" on the CLM Admin Feature Management page and ensure the user has AI Platform credits for extraction to work. For more information, see CLM Quickstart for Platform.

CLM Advantage platform Tools on MCP Server

This feature enables users to access and discover contract lifecycle management information directly through CLM connector and AiMe chat. Users can install Conga CLM connector in Claude and sign in to the Conga CLM connector, to search for contracts, review contract details, track clause changes, discover contract documents and versions, view contract relationships and hierarchies, access contract review information, identify contract team members and responsibilities, discover contract intake requests, and review contract obligations, fulfillments, and related activity history. Chat responses follow the same role-based permissions configured in CLM, ensuring users only receive information they are authorized to access.

The system provides clear, user-friendly responses across supported chat experiences, including consistent fallback messages when requests cannot be answered due to scenarios such as no matching records, ambiguous questions, unsupported fields, out-of-scope requests, tool failures, or access restrictions. Users receive guidance on available actions and next steps instead of technical errors or empty responses. Permission changes made in CLM are reflected in chat responses on subsequent queries, and users receive clear notifications for sign-in failures, session expirations, and requests for information outside their access rights. For more information, see CLM tools on MCP server - Read Tools.

Conversational CLM Access via Chat

This feature enables users to perform contract lifecycle management activities directly through chat. Users can create and update contracts, generate contract documents from templates, attach documents to contracts, manage contract review cycles, send and track contract signatures, activate signed contracts, amend, renew, and terminate active contracts, manage contract obligations and fulfillment records, and query contracts by criteria such as expiration date and value. Contract actions follow existing CLM permissions and access controls and provide clear notifications for permission, validation, and system errors.

Actions that create, modify, delete, terminate, cancel, or notify require explicit user confirmation before changes are committed, including confirmation of the contract, action, and applicable consequences. Users can review relevant documents, recipients, signer details, obligations, and contract information before completing actions, and receive clear results, updated statuses, created records, or completion information after processing. If an action is not fully completed, the system provides a plain-language summary of completed and incomplete steps without exposing raw system or provider error codes. Through chat, only manual review cycles are available. Contract record links are available only in AiME. Uploading a document from your device currently works only in AiMe. For more information see, CLM tools on MCP server - Write Tools.

AiMe as a Contracting Agent

Users can now manage contracts directly in CLM with AiMe, the in-app assistant. Account Executives and Contracting Managers can find, create, and progress contracts in conversation, without working through the usual screens. AiMe follows your existing permissions, configuration, and audit trail. With AiMe, you can perform the following on contracts:

• Create contracts and documents: Describe the contract you need in plain language. AiMe confirms the type, whose paper it is on and the counterparty. After you confirm, it generates the document. If the counterparty supplied the document, AiMe reads its details and asks you to confirm them before creating the contract.
• Find and reuse contracts: Ask AiMe about a single contract or your whole portfolio, and filter by status, counterparty, value, date, owner, or contract type. You see only the contracts you have access to. Answers use the values stored on the contract and never change it. You can also start a new contract from an earlier one.
• Move contracts forward: AiMe proposes the next step based on the contract's status and waits for your confirmation. You can send a contract for legal review or send individual clauses for approval. Reviewer feedback appears exactly as the reviewer wrote it.

The following contract type workflows are supported.

• NDAs: Mutual and one-way NDAs are supported on your own paper and on the counterparty's paper.
• MSAs and work orders: Master agreements and work orders can be created and progressed through review and signature.
• Sell-side agreements: Sales, Order Form, Subscription, License and Reseller agreements are covered. Contracts link to their opportunity or quote. The renewal terms and other details each type needs are collected.
• Buy-side agreements: Purchase, Vendor and Supplier agreements require a known supplier record. A blocked supplier stops the contract.

For more information, see AiMe as a Contracting Agent.

Direct Access to Obligation Details from Email Templates in Supplier Portal

Supplier contacts now receive email notifications with direct links to the specific obligation's Fulfilment Details tab within the Supplier Portal, enabling immediate access to relevant records. Activation emails display only the first fulfilment record when multiple obligations exist, and links are included regardless of the supplier contact's portal access status. For more information, see Obligation Notifications.

Global Document Type Inheritance for Contract Attachments

The assigned document type for a global document (such as "License," "Permit," or "Insurance Certificate") now appears in the contract's Documents tab and all associated records when the document is attached, maintaining consistent classification across contracts. An info icon is added before the Global Document label, displaying the global document's type and description in a pop-over. If no type is assigned, the system continues to display Global Document as the type, and changes at the contract level do not affect the source global document's type. For more information, see Uploading a Document to the Repository and Adding a Global Document to a Contract.

Contract Request Form: UI Validations for Term Type, Start Date, End Date, and Duration

The contract request form now applies term type-based validations for the "Start Date", "End Date", and "Duration" fields, aligning with contract record behavior. For Auto Renew and Fixed Term types, entering a duration automatically calculates the end date, while for Perpetual and Coterminous types, the end date and duration fields are disabled. If no term type is selected, the end date is not calculated based on duration. For more information, see Term Type Validations for Contract Requests.