The system administrator can control access to fields at the page layout level, the user profile level, or field level. These preferences and settings affect whether a user can view and edit specific fields in the CRM. Field access can vary from user to user depending on their initial setup and the configurations made for each profile type.
Here are the permission levels which can be set for each setup configuration:
Field Settings Within Page Layouts
These settings allow you to decide whether a field is visible, required, editable, or read-only for a particular record type.
Field-Level Security
These preferences further restrict field access. Here, you can alter which fields are visible, read-only or none (when neither option is checked).
If Visible is checked, the users can read AND edit the field.
If Visible and Read-Only are both checked, the users can read - but not edit - the field.
If neither option is checked, users cannot read nor edit the field.
These settings override field properties set within the page layout if the field-level security setting is more restrictive.
We recommend that you use field-level security to control users’ access to fields rather than creating multiple page layouts to control field access.
User Profile Permissions
Certain user permissions may override both page layouts and field-level security settings.
For instance, a user with the “Edit Read Only Fields” permission can always edit read-only fields regardless of any other settings. Within the profile view you will find permissions for both standard objects (those native to Salesforce) as well as custom objects (Rethink- or Apto-specific objects).
Editing these permissions will allow you to enable or disable the following abilities for users: Read, Create, Edit, Delete, View All, and Modify All. The animation below will show you where to go within the profile to find these permissions.
