salesforce_security_impl_guide
salesforce_security_impl_guide
salesforce_security_impl_guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Securing and Sharing Data<br />
Field-Level Security Overview<br />
Field-Level Security Overview<br />
Note:<br />
Who Sees What: Field-level Security<br />
Watch how you can restrict access to specific fields on a profile by profile basis.<br />
Field-level <strong>security</strong> settings let administrators restrict users’ access to view and edit specific fields<br />
in:<br />
• Detail and edit pages<br />
• Related lists<br />
• List views<br />
• Reports<br />
• Connect Offline<br />
• Email and mail merge templates<br />
• Custom links<br />
• The partner portal<br />
• The Salesforce Customer Portal<br />
• Synchronized data<br />
• Imported data<br />
EDITIONS<br />
Available in:<br />
• Enterprise<br />
• Performance<br />
• Unlimited<br />
• Developer<br />
• Database.com<br />
The fields that users see on detail and edit pages are a combination of page layouts and field-level <strong>security</strong> settings. The most restrictive<br />
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 <strong>security</strong><br />
settings, the field-level <strong>security</strong> overrides the page layout and the field will be read-only for the user.<br />
Important: Field-level <strong>security</strong> doesn’t prevent searching on the values in a field. When search terms match on field values<br />
protected by field-level <strong>security</strong>, the associated records are returned in the search results without the protected fields and their<br />
values.<br />
You can define field-level <strong>security</strong> in any of the following ways:<br />
• For multiple fields on a single permission set or profile<br />
• For a single field on all profiles<br />
After setting field-level <strong>security</strong> for users, you can:<br />
• Create page layouts to organize the fields on detail and edit pages.<br />
Tip: Use field-level <strong>security</strong> as the means to restrict users’ access to fields; then use page layouts primarily to organize detail<br />
and edit pages within tabs. This reduces the number of page layouts for you to maintain.<br />
• Verify users’ access to fields by checking the field accessibility.<br />
• Customize search layouts to set the fields that display in search results, in lookup dialog search results, and in the key lists on tab<br />
home pages.<br />
Note: Roll-up summary and formula fields are always read-only on detail pages and not available on edit pages. They may also<br />
be visible to users even though they reference fields that your users cannot see. Universally required fields always display on edit<br />
pages regardless of field-level <strong>security</strong>.The relationship group wizard allows you to create and edit relationship groups regardless<br />
of field-level <strong>security</strong>.<br />
36