Having an audit trail/historical data when it comes to workspace configurations/settings would be helpful. Details like what specifically was updated/changed and by whom & when would be great.
Abhinav Bansal
Jul 4, 2025
This audit trail capability is critical given current user management gaps that allow users to potentially escalate their own permissions and make unauthorized changes to templates without proper review.
A comprehensive audit trail for account level section should include:
Section type (Custom Fields, Custom Layouts, etc.)
Object name (specific field or layout identifier)
User (who made the change)
Change type (add, update, delete)
Timestamp (when the change occurred)
Change details (old vs. new values where applicable)
This detailed logging would provide essential governance and accountability for template modifications, helping administrators track and review all configuration changes
As an admin and product owner i would like to review product editing and integrations editing hisory to avoid mistakes and better control when multiple admins/product owners are working on the same products.
Guest
about 6 years ago
in Account settings
0
Future consideration
This audit trail capability is critical given current user management gaps that allow users to potentially escalate their own permissions and make unauthorized changes to templates without proper review.
A comprehensive audit trail for account level section should include:
Section type (Custom Fields, Custom Layouts, etc.)
Object name (specific field or layout identifier)
User (who made the change)
Change type (add, update, delete)
Timestamp (when the change occurred)
Change details (old vs. new values where applicable)
This detailed logging would provide essential governance and accountability for template modifications, helping administrators track and review all configuration changes