Curriculum
Field Level Security is a Salesforce security feature that controls a user’s ability to view and edit specific fields within an object. While users may have access to an object and its records, Field Level Security determines whether they can see certain fields or modify their values.
Organizations often store sensitive information such as salaries, commission amounts, student fees, financial records, customer credit information, and confidential business data. Not every user should have access to this information. Field Level Security provides a powerful mechanism for protecting sensitive data while allowing users to perform their daily responsibilities.
Understanding Field Level Security is essential for Salesforce Administrators because it is one of the most important components of Salesforce Security and User Management.
Field Level Security (FLS) is a Salesforce feature that controls field visibility and edit permissions for users.
Field Level Security determines:
FLS provides more granular control than object-level security.
Organizations manage sensitive information.
Examples:
Without Field Level Security:
Field Level Security helps protect confidential information.
Salesforce security operates in layers.
Controls login access.
Controls object permissions.
Controls field access.
Controls record visibility.
Field Level Security sits between object access and record access.
Example:
Object:
Fields:
User Access:
Can View:
Can View:
Cannot View:
This demonstrates how FLS protects sensitive information.
Field Level Security provides two primary controls.
Determines whether a user can see the field.
Determines whether a user can edit the field.
These settings create flexible access control options.
Users can see the field.
Example:
Customer Email
Displayed on record pages and reports.
Users cannot see the field.
Example:
Customer Credit Score
The field is completely hidden.
This enhances data security.
Users can view the field but cannot modify it.
Example:
Student Registration Number
Users may see:
REG-10001But cannot edit it.
Benefits:
Read-only access is commonly used for important business fields.
Profiles are commonly used to configure Field Level Security.
Example:
Can view:
Cannot view:
Profiles define baseline field access.
Permission Sets can extend field access.
Example:
Profile:
Salary Field = Hidden
Permission Set:
Salary Field = Visible
Result:
Selected users gain access.
This provides flexibility without changing Profiles.
Navigate to:
Setup
Open:
Object Manager
Select Object.
Example:
Student
Select:
Fields & Relationships
Choose Field.
Click:
Set Field-Level Security
Configure visibility settings.
Save.
The changes apply immediately.
Navigate to:
Setup → Profiles
Open Profile.
Select Object Settings.
Open Field Permissions.
Configure:
Save.
This method is frequently used by administrators.
Open Permission Set.
Select Object Settings.
Choose Object.
Configure Field Permissions.
Save.
Users assigned the Permission Set receive the additional access.
Examples:
Field Level Security can be applied to fields within all these objects.
Examples:
Custom object fields can be secured independently.
This provides extensive flexibility.
Object:
Fields:
Permissions:
Can View:
Cannot View:
Can View:
Field Level Security protects financial information.
FLS affects report visibility.
Example:
Salary Field:
Hidden
Result:
Users cannot:
This ensures security across reporting features.
Hidden fields are excluded from:
This prevents accidental exposure.
Field Level Security applies to:
If a user cannot access a field in Salesforce, they generally cannot access it through APIs.
This strengthens security.
Many beginners confuse these features.
Controls display.
Controls security.
Example:
Field removed from page layout:
Users may still access it through reports.
Field hidden using FLS:
Users cannot access it anywhere.
FLS provides true security.
| Feature | Field Level Security | Page Layout |
|---|---|---|
| Security Control | Yes | No |
| Hide Field Completely | Yes | No |
| Controls Reports | Yes | No |
| Controls APIs | Yes | No |
| Controls Display | Partial | Yes |
Field Level Security should always be used for sensitive information.
| Feature | Field Level Security | Object Permissions |
|---|---|---|
| Controls Fields | Yes | No |
| Controls Objects | No | Yes |
| Granular Access | High | Moderate |
| Security Focus | Field Data | Object Access |
Both are necessary components of Salesforce security.
Protect salary information.
Restrict payment data.
Protect patient records.
Restrict scholarship information.
Protect commission data.
Field Level Security supports numerous business scenarios.
Grant minimum required access.
Apply strict controls.
Avoid excessive profile customization.
Review field permissions periodically.
Support compliance efforts.
Verify permissions before deployment.
These practices improve security and governance.
Users gain unnecessary access.
Difficult to manage permissions.
Require strict controls.
Large organizations require careful planning.
Regular audits help address these challenges.
A software training company uses Salesforce.
Object:
Fields:
Access:
Can view Name and Course.
Can view Scholarship Amount.
Result:
Sensitive financial information remains protected while users perform their responsibilities.
This demonstrates the value of Field Level Security.
Understanding Field Level Security helps professionals:
Field Level Security is a critical Salesforce administration skill.
Field Level Security is a Salesforce security feature that controls visibility and edit access for individual fields. By allowing administrators to define which users can view or modify specific fields, Field Level Security protects sensitive information, supports compliance requirements, and strengthens overall Salesforce security. It works alongside Profiles, Permission Sets, Object Permissions, and Record-Level Security to provide comprehensive access control.
Field Level Security controls whether users can view or edit specific fields within Salesforce objects.
It protects sensitive information and ensures users only access data relevant to their responsibilities.
Yes. Hidden fields cannot be viewed in reports.
Yes. Permission Sets can provide additional field permissions.
Field Level Security provides actual security, while Page Layouts only control display.
Yes. Field permissions are generally enforced across Salesforce APIs.
Looking to learn more technologies and programming skills?