Customers may observe that when navigating to Field-Level Security (per profile) or Page Layout → Field Properties for the Name field on any Salesforce object, the Read-Only checkbox is greyed out and non-clickable.. This behavior occurs:
Name field of type Text(80))The Name field is a system-required identity field present on every Salesforce object. The Salesforce platform intentionally disables the Read-Only option for this field in both FLS and Page Layout configurations because:
Name field is relied upon at the platform layer for core record operations (display, search, lookup resolution, list views, etc.).Name field via declarative paths (FLS or Page Layout) is not supported by design.This behavior was confirmed as Working As Designed (WAD)
There is currently no fully declarative, server-enforced way to make the Name field read-only via FLS or Page Layout. The following alternatives can be considered depending on your use case:
Option 1 — Validation Rule (Recommended) Use a Validation Rule to prevent edits to the Name field based on record status or other conditions. This is the most reliable, server-enforced approach.
Option 2 — Dynamic Forms (UI-layer only) Use Dynamic Forms with component visibility conditions to hide the Name field component when a record is in a specific status. Note: this hides the field from the UI but does not enforce read-only at the data layer — the field can still be edited via API or other interfaces.
Option 3 — Record-Triggered Flow A Record-Triggered Flow can revert changes to the Name field when a record transitions to a specific status. However, this approach also requires a Validation Rule as the true enforcement gate to prevent the save from completing.
Important: Options 2 and 3 do not provide server-level enforcement. Only a Validation Rule (Option 1) enforces the restriction at the data layer.
005393595

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.