Change log for configuration updates across the platform
Taylor Jennings
There is no system-wide log of configuration changes in Chili Piper. Admins investigating unexpected behavior have no way to see what changed, when, or who made the change.
Chili Piper should maintain a change log that records configuration updates across the platform, including what was changed, the timestamp, and the user who made the change.
Without a change log, debugging is slow and accountability is unclear. A change log is a baseline expectation for enterprise customers managing complex configurations across multiple admins.
Taylor Jennings
Merged in a post:
Change log to track configuration updates across the platform
Luis Amaral
There is no system-wide log of configuration changes in Chili Piper. Admins investigating unexpected behavior have no way to see what changed, when, or who made the change. Chili Piper should maintain a change log that records configuration updates across the platform, including what was changed, the timestamp, and the user who made the change. Without a change log, debugging is slow and accountability is unclear. A change log is a baseline expectation for enterprise customers managing complex configurations across multiple admins.
Taylor Jennings
Merged in a post:
Change log visibility
Provide a change log for assets that describes what changed, when, and who changed it.
Taylor Jennings
Merged in a post:
Audit trail for routing rule changes
Taylor Jennings
There is no record of when routing rules were changed or who made the change. Admins investigating unexpected routing behavior have no way to trace it back to a configuration change.
Chili Piper should maintain an audit trail that logs routing rule changes, including what was changed, when, and by whom.
Routing rules are high-stakes configuration. Without an audit trail, debugging is slow, accountability is unclear, and teams have no recovery path when a bad change causes routing failures.
Luis Amaral
Hi @ally Hardesty we neither use char or distro, so this would apply to the admin (user management), concierge , chilical and handoff
Luis Amaral
This is critical to our organization. We have multiple workspaces with multiple user with an overarching admin team (us) that manages all those workspaces, but we currently have NO WAY to track whenever someone makes a change and what that change was. This would be critical, especially for concierge routers, which already has had significant implications for our organization. Please add logs to concierge routes the same way you did for Chat&distro