Description -
Currently, Workfront's Audit Logs primarily track actions performed by individual users. While recent enhancements (specifically the "Other enhancements during the Second Quarter 2025 release timeframe" regarding Represent Adobe Admin Console user changes as "System" in the Workfront update feed) have introduced "System" activity updates in user update feeds, and these actions captured in the comprehensive System “Audit Log,” however, it’s no longer possible to filter for these log types and action performed by “System” listed under the User Name column.
Why is this feature important to you -
This highlights a critical visibility gap regarding automated or system-driven changes within Workfront. For example, changes originating from integrations, API calls, automated workflows, or even internal Workfront system updates are not readily auditable through the Setup > System > “Audit Log” page.
Improved Transparency and Accountability: Gain a comprehensive understanding of all system-driven changes within Workfront.
Enhanced Troubleshooting and Issue Resolution: Quickly identify the source of unexpected changes or errors.
Strengthened Security and Compliance: Maintain a detailed record of all system activity for audit and compliance purposes.
Increased Integration Visibility: Track changes made by integrations and API calls for better management and troubleshooting.
How would you like the feature to work -
We propose the creation of a dedicated, filterable "System" Audit Log within Workfront, mirroring the functionality of the existing user-based Audit Log. This log would:
Capture all system-initiated actions: This includes changes made by integrations, API calls, automated workflows, internal Workfront system updates, and actions attributed to the "System" user as seen in the user update feeds (e.g., Adobe Admin Console user changes).
Provide detailed information: Similar to the user Audit Log, this log should include timestamps, action types, affected objects (projects, tasks, users, etc.), and relevant details of the changes made.
Offer robust filtering and search capabilities: Users should be able to easily filter and search the log based on various criteria, such as date range, action type, affected object, and integration/system source.
Maintain a consistent format: The log should adhere to a clear and standardized format, making it easy to understand and analyze.
Respect existing access controls: Access to the System Audit Log should be governed by appropriate permissions, ensuring data security and compliance.
Current Behaviour -
The recent change to represent Adobe Admin Console user changes as "System" in the Workfront update feed highlights the need for a dedicated “System” Audit Log. While this change is a positive step, it underscores the lack of a centralized location to track all Workfront system-initiated actions.
We’ve confirmed with support that, “The reason, we are unable to search for “System” it's only a text string, and it's not a user. This will need to be a feature request, since the audit logs, are designed to only search for Workfront user objects.” and that it’s not currently possible to access this information via the API.
Call to Action -
Please vote for this idea to enhance Workfront's audit capabilities and provide greater transparency into system-driven changes. This will empower administrators and users to better manage and troubleshoot their Workfront environment.
