OneTrust Activity Log
The OneTrust Activity Log feature is limited to users with the Site Admin role.
Overview
The OneTrust Activity Log delivers a unified, real-time view of user and system audit events across the OneTrust platform, helping administrators increase visibility and control, investigate issues faster, and meet compliance requirements with a complete, traceable audit trail. Through a centralized audit experience, teams can quickly search and filter audit records, monitor activity across solutions from a single location, and export audit data for broader reporting and analysis.
Captured activity and events
As of the OneTrust 202611.1.0 release, the Activity Log records activity across supported areas such as authentication, sessions, credentials, user and organization management, risk, branding and email settings, domains, and language settings. Document downloads and file attachments are also recorded. Coverage depends on the supported product areas and object types. Use the API endpoint to retrieve supported event types.
Activity information is also available in the activity tabs of supported product areas, such as users, organizations, and risks. In these areas, you can filter an entity's activity by event type when the option is available.
Record retention periods
Global Audit records are retained for one year in standard environments and seven years in HIPAA environments. This retention policy takes effect on [confirmed effective date].
To access audit records older than the retention period, use the reporting area to export records by model or object type.
Integration events and legacy trigger deprecation
Global Audit records are available through integration events. Use an integration workflow to send audit data to a webhook or an Amazon S3 bucket. The Activity Record Created trigger provides audit information in a format intended for SIEM tools.
The Activity Record Created (Legacy) trigger will be supported alongside the standardized audit event (known as Activity Record Created until the Spring '27 release. After that transition period, the legacy event is planned for deprecation. If your integration uses the Activity Record Created (Legacy) trigger in your integrations, you will need to update them with the standardized audit event before deprecation.
Accessing the Activity Log
It may take a few minutes for logged events to appear in the Activity log screen. Refresh to populate new results.
Auditing Activity Actions
You can retrieve a complete list of the event names currently available via the public API endpoint. This approach is useful when you want a reusable export of event names for compliance review, rule mapping, or downstream analysis outside the OneTrust platform.
Prerequisites
-
Access to a developer tool such as Postman
-
Client Credentials configured with the
AUDIT_LOGscope. For more information, see Managing OAuth 2.0 Client Credentials.
Configuring the API
Impacts & Considerations for OneTrust Products
Consent & Preferences - DS GUIDs
Global Activity is designed to provide centralized visibility into platform activity without storing personally identifiable information in the audit layer. Because of that design, consent-related audit records for data subjects are not searchable by familiar personal identifiers such as an email address or values.
This approach helps limit unnecessary exposure of personal data in Global Activity while still preserving the audit trail needed for investigation and review. When a user needs to find audit activity related to a specific data subject, they must search using the data subject GUID (DS GUID) instead of the personal identifier. The DS GUID is the system-level identifier available to Global Audit and is the supported value for locating the relevant audit record.
-
Locate the DS GUID for the data subject in the source data subject record or related workflow.
-
Open Global Activity and go to the search or filter experience.
-
Enter the DS GUID as the search value instead of the email address or other personal identifier.
-
Review the returned audit records to find the relevant activity for that data subject.
Tenant Copy & User IDs
A current limitation of tenant copy with Activity Logs is that some historical audit records may retain source-tenant userIDs instead of mapping cleanly to userIDs in the target tenant, which can cause missing or incomplete user details in audit history after the copy.
For more information, see Submitting a Tenant Copy Request.
Activity Log FAQ
Can I export Global Activity logs?
Yes, you can export events in real time to SIEM via Integrations. Although HTTP POST request URLs are the primary documented method for sending Activity Log data to external SIEM tools, Workflow Builder supports multiple integration patterns. Depending on the use case, you can use seeded SIEM connectors from the Gallery, apply filtering and transformation logic before delivery, route events through reusable subflows, or leverage other supported integration targets and export mechanisms.
For more information, see Integrating OneTrust Activity Logs with External SIEM Tools.
Will Global Activity logs replace the Activity tabs available across the platform?
No, it will not replace Activity tabs within individual solutions. Global Activity provides a central view and does not replace activity tabs within individual product areas. In supported areas, you can also filter an entity's activity by event type from its activity tab.
Can I filter the Global Activity log by specific product without navigating to that product's menu?
Yes. You can filter by one or more product areas from the solutions subscribed to by your tenant. Selecting a product area narrows the available record types and activities to those supported for that area.
For records that are updated using client credentials, will the activity log show which client credentials were used?
Not currently. The Performed by details show the user's name, email address, and the time of the activity. Displaying information about the client credentials used for an operation is planned for a future release.
What information does OneTrust log for client credentials?
Network details in an activity record can include the domain or custom subdomain, user-agent information, and the user's IP address. These details do not identify which client credential was used; client-credential information is not currently displayed in the Performed by section. Integration-initiated SIEM payloads may not include the original network context.
For records that are updated via integrations, will the activity log show which workflow triggered the update?
Yes. For operations performed by an integration workflow, the Trigger details section identifies the workflow, event type, and trigger type. Other trigger sources are not currently described as supported.
What happens if the record associated with an activity has been deleted?
The activity record remains available. If you select View Record for an entity that has been deleted, OneTrust opens the not-found page for the relevant product area.
How does the organization filter work?
The organization filter returns records associated with the organization you select. It does not include records for parent or child organizations. Records for object types that are not associated with an organization can show a null organization value.
What is changing about the Activity Record Created integration event?
Activity Record Created (Legacy) is the previous audit integration event. A standardized audit event (Activity Record Created) is also available for sending audit information to SIEM tools. We plan to support both event formats until the Spring '27 release. After the transition period, the legacy event is planned for deprecation. If your workflow uses Activity Record Created (Legacy), update it to use the standardized event before the legacy event is deprecated.
How long are Global Audit records retained, and can I access older records?
Global Audit records are retained for one year in standard environments and seven years in HIPAA environments, starting [effective date]. To access records older than the retention period, use the reporting area to export records by model or object type.