Users see fields in list views that are hidden in the page layout

Explanation 1:

In Professional, Enterprise, and Unlimited Editions, administrators can specify that certain fields are not displayed in the page layouts for their Users. Normally if a field is hidden in the page layout, it will not be accessible as a column header in a list view. However in list views, Users can see required fields that are "derived" from associated records, even if the field is hidden in their page layout.

Note: In Professional Edition, the field must be in the page layout to display in a list view.
In Enterprise, Developer, and Unlimited Editions, Field Level Security determines whether or not the field is visible.

Example:

• If you hide the 'Account Name' field on the Cases page layout, Users can still display the 'Account Name' in a Case list view.
• This is because the 'Account Name' field is a required field for contacts, and the 'Contact Name' is required for the Cases page layout. Therefore, the 'Account Name' is derived from the Contact on a Case, and it cannot be hidden in a list view.

Explanation 2:

In Enterprise Edition, using field-level security, administrators can specify that a field may be visible for a particular profile, but hide that field from the user on the page layout. This way, a User may still report on the field, but not visible on the record detail or edit page.


See also:
Field-Level Security
Control User Access to Fields