Hi,
The following approaches come to my mind that you could investigate. It also depends how many users should turn this off and on - can you give us an approximate number?
1.: Add database log. This doesnt prevent users from changing something else, but gives you visibility what else was changed
2.: Electronic signatures slows the process of changing down. That means, when a users changes something on the table, he needs to sign it, i.e. puts in a reason. That gives him some time thinking if he really wants to make changes on the correct field. Its more an extension to the database log. Details can be found here: D365 Electronic Signatures: One of the Most Underrated Security Features | Kurt Hatlevik – Dynamics 365 Blog
3.: In case there is an entity for this parameters, you could use Power automate (PA) to restrict this. The idea is the following. You create a PA flow that is being triggered manually. The input parameters is either yes or no. The trigger is only triggered if certain people do that - you have to create a condition in your flow. The flow can be shared with the key users. Others usually wont trigger it as you havent shared it with them. Even if the flow is reshared, the condition prevents it from others doing it. Once the flow is triggered the parameter change is being done by a service user. Its an idea, I havent implemented it myself.
Kind regards, Adis
If this helped, please mark it as "Verified" for others facing the same issue
Keep in mind that it is possible to mark more than one answer as verified
