Unexpected Risk Reopen by System Administrator – How to Prevent This?

[vallabha180]

Hello,
We recently observed that the System Administrator reopened risks RK0021440 and RK0021427, moving them from Retired to Draft on December 12 at 10:55.
1. Why did this happen?
• Are there any system processes, business rules, or workflows that could have triggered this?
2. How can we prevent this from happening again?
• Is there a way to restrict reopening risks that are in the “Retired” state?
3. Were other risks also reopened by System Administrator?
• How can we check if more risks were affected?
4. Can we reverse these changes?
• If other risks were also reopened, how can we move them back to the Retired state?
Any insights or best practices would be appreciated.

Thanks!

[J Siva]

Hi @vallabha180 

It varies based on the related records.

Look for the related which're updated on the same time.

One of the scenarios would be the change in status of issue record related to that risk.

There could be other scenarios as well like change in status of control records, tasks etc