Security Implementation Guide

Security Overview
Securing and Sharing Data
User Permissions and Access
Revoking Permissions and Access
Profiles Overview
Enhanced Profile User Interface Overview
Working with Profiles in the Original Profile Interface
Viewing and Editing Tab Settings in Permission Sets and Profiles
Enable Custom Permissions in Profiles
Assigning Record Types and Page Layouts in the Enhanced Profile User Interface
Permission Sets
Object Permissions
Field-Level Security Overview
Setting Field Permissions in Permission Sets and Profiles
Setting Field-Level Security for a Single Field on All Profiles
Field Permissions
Classic Encryption for Custom Fields
User Permissions
Desktop Client Access Overview
Setting Login Restrictions
Managing Salesforce Classic Permissions
About Organization-Wide Sharing Defaults
Setting Your Organization-Wide Sharing Defaults
External Organization-Wide Defaults Overview
Sharing Rules Overview
User Sharing Overview
Roles Overview
About Groups
Creating and Editing Groups
Group Member Types
Viewing All Users in a Group
Granting Access to Records
Configuring Salesforce Security Features
Enabling Single Sign-On
Monitoring Your Organization's Security
Security Tips for Apex and Visualforce Development
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Field-Level Security Overview

Available in: Enterprise, Performance, Unlimited, Developer, and Database.com Editions

Watch Video Demo Who Sees What: Field-level Security

Watch how you can restrict access to specific fields on a profile by profile basis.

Note

Field-level security settings let administrators restrict users’ access to view and edit specific fields in:
  • Detail and edit pages
  • Related lists
  • List views
  • Reports
  • Connect Offline
  • Email and mail merge templates
  • Custom links
  • The partner portal
  • The Salesforce Customer Portal
  • Synchronized data
  • Imported data

The fields that users see on detail and edit pages are a combination of page layouts and field-level security settings. The most restrictive field access settings of the two always apply. For example, if a field is required in the page layout and read-only in the field-level security settings, the field-level security overrides the page layout and the field will be read-only for the user.

Field-level security doesn’t prevent searching on the values in a field. When search terms match on field values protected by field-level security, the associated records are returned in the search results without the protected fields and their values.

Important

You can define field-level security in any of the following ways:
After setting field-level security for users, you can:
  • Create page layouts to organize the fields on detail and edit pages.

    Use field-level security as the means to restrict users’ access to fields; then use page layouts primarily to organize detail and edit pages within tabs. This reduces the number of page layouts for you to maintain.

    Tip

  • Verify users’ access to fields by checking the field accessibility.
  • Customize search layouts to set the fields that display in search results, in lookup dialog search results, and in the key lists on tab home pages.

Roll-up summary and formula fields are always read-only on detail pages and not available on edit pages. They may also be visible to users even though they reference fields that your users cannot see. Universally required fields always display on edit pages regardless of field-level security.

The relationship group wizard allows you to create and edit relationship groups regardless of field-level security.

Note