Improve the existing confirmation prompt / add new ones wherever possible for sensitive user actions to include clear impact details and next steps, and introduce traceable audit logs for all such actions.
Problem Statement
For eg: A confirmation prompt already exists for actions such as widget API key regeneration. However, the current message, “This will replace the current token and cause any code referencing the old token to not work as expected,” is insufficient. It tells the user what will break but does not tell them what they need to do next, to update it across their external sites and integrations; otherwise, they will stop working immediately.
Additionally, there is no accessible audit trail capturing when such actions occurred, who performed them, and what changed. When issues arise, the customer cannot independently verify what happened, requiring escalation to the product team for backend log access each time.
Proposed Improvements
Enhanced confirmation prompt: Expand the existing warning to include the full impact and the required next steps. Example: “Regenerating this token will immediately invalidate the current key. Any websites or integrations using the old key will stop working until you update them with the new key. Please ensure you update the widget script on all external sites after regenerating. For guidance, refer to [link to documentation]. Do you want to continue?”
Traceable audit logs: Maintain a comprehensive, timestamped activity log at the project and team level that captures all sensitive user-initiated actions, including the action performed, the user who performed it, the timestamp, and the before/after state where applicable. This log should be accessible to project admins.
Expected Outcome
  1. Users are fully informed of the impact and their required next steps before completing a sensitive action
  2. Accidental or uninformed changes are significantly reduced
  3. Customers can independently verify what happened and when