Audit and Access Dashboard
The Audit and Access Dashboard allows you to monitor and review all tracked changes to key CLM records, such as contracts, suppliers, supplier requests, tasks, and so on.
This dashboard helps you to monitor details about who created or updated a record, when the change occurred, and what data was added, changed, or removed. The feature ensures transparency and supports audit and compliance requirements.
Audit Tracking
Administrators must enable audit tracking through platform configuration for various objects, such as Contracts, Suppliers, Supplier Requests, Task, ConversationThread, ConversationMessage, ConversationParticipant, and so on, to record changes to key records and configurations. These changes are displayed in the Audit and Access Dashboard, allowing you to review who made a change, when it occurred, and what was updated. For more information on configuring audit tracking, see Audit and Access Dashboard Configuration.
Dashboard Overview
- use the Filter icon to refine audit results based on Date or time range, Username, Object Name, Field Name and so on.
- sort columns to quickly identify recent or critical changes, and
- download reports for offline review or compliance reporting.
The dashboard organizes audit information into the following sections for easier review and analysis.
-
User Login Activity: Displays user login trends within the organization. This section displays Username, Timestamp, User Type, and so on. Data is retained for the past 60 days based on login history.
-
Data Change History: Displays field-level changes for objects and fields configured for audit tracking. Data is available for the past 30 days.
This section displays Username, Timestamp, Object Name, Record Name, Field name, Action Type (Create, Update, Delete), Old Value, New Value, and so on. For each record, the system automatically logs CreatedBy, CreatedDate (when created) and ModifiedBy, ModifiedDate (when updated).Note:When you delete a post in Conversations, the system performs a soft delete; the post is hidden but remains in the database. If the post is part of a conversation, the associated conversation is also removed from view.
- Deletion of a conversation post is logged under ConversationThread object.
- Deletion of a response to a post is logged under ConversationMessage object.
Following examples illustrate how system or user initiated changes appear once the relevant fields are enabled for auditing.- Updating a supplier record: When the status of a supplier record transitions from Pending to Active, the system records an audit entry as follows:
Field Example Value Object Name Supplier Field Name Status Old Value Pending New Value Active Modified By Username (of the user who made the change) Modified Date Timestamp -
Adding a new field: When an administrator adds a custom field
Websiteto the Supplier object (via configuration update), the system records the audit trail as follows.Field Example Value Object Name Supplier Field Name Website Old Value --- New Value www.conga.com Modified By Username (of the user who added the field value) Modified Date Timestamp
-
Configuration Change History: Displays audit details for system configuration changes captured through the same audit framework. This section displays Username, Timestamp, Full Name, Configuration Category, and so on. Data is available for the past 30 days.