Update the permitted fields on a customer profile
An operator edits the customer profile fields they are permitted to change; identity-defining and protected fields stay read-only unless the operator also holds the protected-fields permission.
When this happens: Operator clicks Edit on the customer profile panel or the Contact detail page.
Step by step
- 1
Click Edit on *Maria Popescu*'s profile.
EasyCRM shows the edit form: permitted fields (phone, mobile phone, email, job title, department, address, language, description, tags) are editable; protected fields (first name, last name, company, owner, consent flags) show read-only with a lock affordance.
- 2
Update the phone number and job title.
- 3
Click Save.
EasyCRM checks the input, re-checks that only permitted fields changed, saves, and writes
ContactUpdated.
Other paths
Actor holds editprotectedfields
If an actor holding EasyCrm.Contacts.EditProtectedFields also sees first name, last name, company and owner as editable, matching FR-02-008.
If something goes wrong
Protected field submitted without permission
If the request includes a change to a protected field from an actor without EditProtectedFields (e.g. A direct API call). The protected field's stored value is kept; permitted fields still save; the response lists the field(s) that were not applied.
Good to know
- Permitted fields are editable by any holder of
EasyCrm.Contacts.Edit; protected fields also requireEasyCrm.Contacts.EditProtectedFields. - The check is enforced server-side per field, not only by hiding controls. (FR-02-022; BRD §8 rule 11)