Opportunity Fields > "Field Label/name" > Set Field-Level Security >
What is Visible vs Read OnLy?
A Google Search Revealed:
Visible : If you check the "Visible" checkbox, that field will be visible to that profile. User can read & edit that field
Read-Only: If you check the "Read-Only" checkbox, that field will be read only for the users of that profile. User can only see that field, he can't edit. Field must be Visible to be Read-Only
^That confuses me…
I want The profile to only be able to see The field; Not Edit it. But I can't Select "Read Only" Unless I select "Visible" But "visable" allows them to edit it.
Best Answer
The hierarchy of permissions shown in this particular facet of the Salesforce UI is a bit backwards compared to the way we usually talk about permissions. Most of the time, when talking about CRUD/FLS permissions, we understand that there are four different rights at the object level, where Read < Update < Create < Delete, and two at the field level, where Read < Edit. We also always talk about permissions as additive; we don't use the permissions system to take away rights.
In this specific context (as well as in the custom field creation wizard and the properties dialogue for fields shown on a page layout), it works the other way. "Read Only" is an extra layer on the basic "Visible"; "Visible" means Read and Update permission; and "Read Only" removes the Edit facet. This is backwards relative to the FLS editor within a user profile, although it still records the actual permissions the same way under the hood.
In your use case, you should check both boxes.