Improved Team Auditing filtering and functionality
backlog
E
Expected Condor
The Team Auditing log has so much useful information, and we use it as a main reference point for article changes, but the filtering and functionality could use improvement.
1) In addition to filtering by individual user, it's imperative we have the option to filter by KB/workspace. Each person on our team manages multiple workspaces, so if I were to view audit information on my own activity, it would list articles across different workspaces. So there's no way for me to isolate audit activity to just one workspace.
2) As part of the log information in grey (user, publish date, and language), it should also list the workspace the audit entry belongs to. This would help me visually isolate entries for one workspace, and would be especially helpful if the workspace filtering functionality needs more time to be implemented. In addition, we have some generic articles that may have the same title across our different product's workspaces (e.g. "Getting Started" or "FAQ") so identifying the workspace it belongs through within the entry is necessary to know which article it even references.
Thank you! :)
Log In
D
D360 Product Management
marked this post as
backlog
K
Kavya
Hi Expected Condor,
Thank you for sharing this detailed feedback. We understand how central the Team Auditing log is for tracking article changes, especially when team members work across multiple workspaces.
The points you raised—particularly the need to filter audit logs by KB/workspace and to clearly display the workspace name within each audit entry—make a lot of sense. This would significantly improve clarity, especially in cases where:
A single user manages multiple workspaces, and
Articles share common titles across different products or workspaces.
We can see how the lack of workspace context today makes it harder to isolate relevant activity and interpret audit entries accurately.
We’ll take this feedback as an improvement request and review it with the product and engineering teams to assess feasibility, effort, and prioritization. In the meantime, adding workspace information directly to each audit entry is a helpful suggestion that we’ll keep in mind as a potential interim or complementary enhancement.
We’ll share an update once we have more clarity on next steps. Thanks again for outlining the use case so clearly—it’s very helpful
E
Expected Condor
Kavya Of course! Excited for any potential updates.