@Mention Tagging for Non-Participant Users in Conversation Threads

The @mention drop-down in the rich text editor now displays all searchable users, clearly distinguishes thread participants from non-participants, and filters out user groups. When users submit or edit messages that include @mentions of non-participants, a Grant Contract Access confirmation pop-up lists those users, indicates whether they receive read-only contract access, and allows users to remove mentions before submission. The system integrates this confirmation and validation process into the reply, edit reply, and edit post flows. For more information, see Editing a Post, Replying to a Post in the Application, and Editing a Response to a Post.

Conversation Reports Export Enhancements for Contracts

You can download conversation logs from the Conversations Report under Reports & Dashboards. Each export includes message details, sender/recipient info, participant counts, tags, and attachments.

Contract numbers display correctly, and some column names have been updated for clarity. Time zone can be selected during export, but downloaded reports reflects only UTC time zone. Only permitted users can export, and any missing data due to restrictions will be flagged with a warning in the file. For more information, see CLM Report.

Permission Sets for Conversations

Separate permission sets has been introduced to provide distinct roles for read-only and create/edit access.

Administrators can assign the Conga Conversations Read Only Permission Group to allow users to view posts, attachments, and responses, and the Conga Conversations User Permission Group to allows users to create, edit, and respond within Conversations. For more information, see Roles and Permissions.

Contract Number-Based Filtering in Conversation Threads

Contract Managers can now filter conversation threads by contract number across all workflow states, enabling consistent identification of agreement-related discussions. The UI displays the contract context in thread summaries for improved clarity. For more information, see Filtering Conversations by Contract Number.

Workflow Activity Reassignment Button and Configuration Updates

You can now reassign an active workflow step to another user or user group directly from the CLM application, without restarting the workflow. This is useful when the assigned user is unavailable, has left the team, or when responsibilities have changed. To support this, the following workflow activities now include a new Allow Reassignment option in their configuration settings: Approval, Interactive Decision, CLM Send for Review, CLM Implicit Interactive, Document Generation, and Esignature. When a reassignment occurs, the platform notifies both the previous and new assignees and logs the change in the audit trail.

The workflow chevron and stage details update in real time to reflect the new assignee, notifications are sent to the new assignee, and all reassignments are logged with audit details including previous and new assignees, reason, timestamp, and the user or system performing the reassignment. The previous assignee loses access to stage actions after reassignment, and error handling prevents invalid reassignments. For more information, see Use Case: Workflow for Send for Review Activity.

Overdue Obligation Notification for Assignees

The system sends a one-time overdue notification to obligation assignees when an obligation remains unfulfilled for 7 days after the due date and has Pending Fulfilment status. Notifications are grouped by user and contract, and each assignee receives a single consolidated email per day at 10 AM, excluding obligations linked to expired, terminated, canceled, or inactivated contracts. The notification uses a standardized email template and includes a direct link to the Fulfilment page within the contract record. For more information, see Obligation Fulfillment.

Role-Based Access Control for Conversations on Contract Requests and Supplier Requests

Administrators can now define and manage role-based access control (RBAC) for Conversations on Contract Requests and Supplier Requests, supporting granular permissions for internal and external users. Internal users with request access can participate fully in conversations, while non-participants have read-only access until added; external users can be added as participants via email reply but are not visible in the application participant list and cannot add internal users. For more information, see Roles and Permission Groups.

Add Global Documents as Attachments in Conversations

Collaborators can now attach global documents when creating, editing, or replying to posts in Conversations related to contracts. For more information, see Creating a Post, Editing a Post, Replying to a Post in the Application, and Editing a Response to a Post.

@Mention Tagging in Collaboration Posts

Tag internal users in posts and replies using the @mention feature in the rich text editor. Tagged users are automatically added to the participants list if not already present, and the @ symbol appears next to their names in posts, threads, and notification emails. Only existing participants can be tagged, and removing a tag before posting removes the user from the participants list if newly added. For more information, see Conversations.