Add more details to Admin Actions in console Endpoint Protector

What is a one sentence summary of your feature request?

Add more details to Admin Actions in console Endpoint Protector

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

We would like the EPP console to provide the ability to view detailed information about the changes an administrator makes to a policy. In particular, it would be useful to see which specific parameters were modified by the administrator within a particular policy.

For example, the console could highlight the exact changes made by the administrator. Currently, the Administrator Actions section displays general fields such as Policy Name and other related fields; however, this is not sufficient to fully understand what specific changes were made.

What we mean is that if an administrator changes a specific field in a policy, for example Exit Points, the Administrator Actions section should display specific information indicating that the Policy Exit Points field was changed.

This approach would allow us to analyze administrator actions more quickly, track changes more accurately, and simplify the audit of policy modifications.

How do you currently solve the challenges you have by not having this feature?

Currently, in order to analyze what was changed in a policy, it is necessary to download two Administrator Actions reports and manually review which items were modified. This slows down the investigation of administrator actions that may have led to a system malfunction, for example.

Upload any supporting images that you think should be considered in this idea.

4 Likes

Hi Nadia,

Thank you for the detailed write-up and the supporting screenshots — they make the problem very clear.

You’re right that the Before/After comparison in the console currently doesn’t surface all the fields that were modified, which forces administrators to download and manually compare two separate PDF exports to understand what actually changed. That’s a legitimate audit pain point and the approach you’re describing — having the console highlight the specific fields that were modified — is exactly the right direction.

We’ve reviewed this internally and it’s something we’re planning to look into. We don’t have a timeline to share yet, but we’ll update this thread as there is progress.

Thank you again for the thorough submission.