Publisher Attribution for Knowledge Base Versions


Each knowledge base version now records who published it.
How It Works
Whippy now captures and displays the user who publishes each knowledge base version. When a version is pushed live, the system automatically records the publisher and associates that user with the published version. This happens at the time of publishing and requires no changes to existing workflows or permissions.
For versions published before this update, publisher details may not appear because that data was not previously tracked.
Why It Matters
Teams often collaborate on knowledge base content, with one user drafting and another approving or publishing. Previously, there was no reliable way to see who actually published a version. This update improves visibility and accountability by clearly showing who pushed each version live, which helps with audits, content reviews, and internal ownership.
This change supports better content governance across shared knowledge bases and aligns with Whippy’s focus on clear, trackable communication management.