Sign in to Community
Sign in to view all badges
Expand my Community achievements bar.
We would like the ability to see who and when changes are made to system wide settings within our instance.
Yes, audit trails across the entire application would be awesome as well. It can be really hard to know how something got into a state that it did without knowing who set the status of this project / task / issue to what when.
This is especially important to changes made to custom fields, forms, and sections. Currently, no audit trail is created to fields that are modified or deleted. It would be helpful if this extended all the way down for fields to include values for drop-down, check-box, and radio button fields. Also changes to calculations for calculated custom fields as well as field access and logic changes and form setting changes.
Yes - this would be very helpful!
This thread is similar - https://support.workfront.com/hc/en-us/community/posts/115004101853-Download-Report-on-configuration...
Hi Ciaran and everyone else who has contributed to this product idea,
We have reviewed this idea with careful consideration of the impact this capability has on our customers and their ability to leverage Workfront most effectively within their organizations. While we are in the process of deploying new capabilities to audit key security-related changes (e.g. changes to access levels, users, and group membership) within Workfront (please refer to Viewing Audit Logs Help article for more information), unfortunately we do not have plans in the next 12 months to implement an audit trail related to changes to system properties accessible within the Workfront interface.
We are continuing to invest in areas that enable a system administrator to delegate certain permissions and processes to group administrators to limit the number of required system administrators within each customer instance. We suspect that this will help our customers limit un-intentional impacts to system settings.
@Miramparonyan - I appreciate your consideration, but I think your team may have missed our concerns. I don't want the ability to push System functionality out to more people. I want to keep it limited! I also want to track it. I want to know exactly when an SSO certificate was changed and who changed it. I want to know when a project status was added, what it was and who added it. I don't want just anyone to be able to add project statuses or milestone paths. Those significantly impact reporting across multiple people. I don't want people to be able to adjust branding without it being tracked. These are configuration changes and I want an audit trail. Can you please reconsider?
I concur with Jennifer Stevens. I also am not advocating the ability to push out more updates. I want an 'audit trail' of changes - to know what change was made, who made then & when.
Agreeing with Jennifer and Marie....as a system admin, I want to see an audit trail for all items appearing in Setup menu of Workfront.
@Jennifer Stevens, Marie Kelly and Kelly Wehrmann,
Thanks for the additional feedback. We recognize the need to make audible some key changes in the Setup area. Though the main reason this product enhancement status was set to "Not Planned" is that due to other product priorities there will not be audit trails tracking changes to System preferences, milestone paths, statuses, etc. implemented in the next 12 months (definitions of Idea statuses can be found at the Idea Exchange landing page). Instead, we are likely to first enhance the upcoming System Audit Logs solution designed to track user-triggered changes impacting other users's permissions in the system (e.g. changes to Access Levels).
Hope this helps.
@MariamParonyan not wanting to keep going round and round -- but in large enterprise environments where multiple instances are being used. Such as @JenniferStevens; and my instance these controls or rather checks and balances are critical for future growth and adoption <just speaking for my side>. Security auditing is one of the weaker areas of the tool from an Admin perspective.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.