When a field is on Notify or Revert, changing it inside MX still works the usual way: someone edits the location or sends a Bulk Update request, and the change goes to Approvals. Protect adds two rules.
Decide a change to a locked field
- A change to a locked field is never approved automatically, whatever your Automations settings.
- Approvers can’t approve or reject it. In Approvals they see “Only an Owner or Admin can decide a protected field”, and on the location’s page they don’t get Approve and Reject for it.
- A Bulk Update request that changes a locked field at any of its locations needs an Owner or Admin to decide the whole request.
Owners and Admins approve or reject these changes in Approvals as usual.
Check the new protected value
When an approved change is applied while the field is still locked, MX makes the new value the protected value for that location and field. Protect never reverts your own change as if it came from outside. If a change to that field was still open in Protect’s Activity, it closes as Replaced by an MX change.
The location’s Location change activity shows “Protected value updated by an MX change”.