Suggestion: State Change Approval Process

[uthornbl]

For many organisations it simply isn't viable to grant a user permission to switch Features on and off at will.
It needs to be a controlled process, often backed by a ServiceNow change request (alternatively a ServiceNow incident)
At the very least it would require a 4-eyes procedure (on the lines of ADO YAML pipelines) where you can enforce that an approver needs to confirm your Feature enable/disable action.

For each Environment where approvals have been enabled, an Approver would be defined as a user with WRITE access to that same Environment, while NOT being the Instigator of the requested state change (Enabled=>Disabled or Disabled=>Enabled)

An Instigator would request a state change. The request would then enter a Pending state, while waiting for an Approver to approve the state change request. If, for compliance reasons, a ServiceNow CHG is required, it's the responsibility of the Approver to double check such an approved CHG exists, and is in the Implement state.
Here, a new menu option like "My Pending Approvals" would be useful.

As soon as an Approver approves a state change request, the affected Feature would be enabled/disabled as appropriate.

Happy to elaborate further on this model if required.

/ Ulf.