Loading

`Name` Field Cannot Be Set to Read-Only via Field-Level Security or Page Layout

Дата публикации: Sep 2, 2026
Описание

Issue / Symptom

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:

  • On custom objects (e.g., a custom Name field of type Text(80))
  • On standard objects (e.g., Account Name)
  • Regardless of the profile or permission set assigned to the user
  • Even after ruling out the "Edit Read-Only Fields" system permission as a bypass — the checkbox itself is disabled, not merely overridden

Root Cause / Explanation

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:

  1. The Name field is relied upon at the platform layer for core record operations (display, search, lookup resolution, list views, etc.).
  2. Enforcing read-only on the Name field via declarative paths (FLS or Page Layout) is not supported by design.
  3. This restriction applies platform-wide — it is not object-specific, org-specific, or profile-specific.

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

 
Загрузка
Salesforce Help | Article