Curriculum
Data Security and Field-Level Security are fundamental components of Salesforce administration that help organizations protect sensitive information while ensuring users have access to the data they need. Every organization stores important business information in Salesforce, including customer records, employee details, financial information, sales opportunities, and confidential business data.
Without proper security controls, unauthorized users may gain access to sensitive information, leading to compliance issues, data breaches, and business risks. Salesforce provides a robust security model that allows administrators to control access at multiple levels, including organization-wide settings, profiles, roles, sharing rules, object permissions, record access, and field-level security.
Understanding Data Security and Field-Level Security is essential for Salesforce Administrators, Developers, Consultants, Security Architects, and Business Analysts because security is one of the most important responsibilities in any Salesforce implementation.
Data Security refers to the processes, policies, and technologies used to protect Salesforce data from unauthorized access, modification, deletion, or exposure.
The goals of data security include:
Data security is a critical part of every Salesforce deployment.
Organizations manage valuable information.
Examples:
Without proper security:
Strong security controls help protect organizational assets.
Salesforce uses multiple layers of security.
Controls login access and authentication.
Controls access to objects.
Controls access to fields.
Controls access to records.
Extend record access.
These layers work together to provide comprehensive protection.
Object-Level Security determines whether users can:
Example:
User can access:
User cannot access:
This level of control is managed through Profiles and Permission Sets.
Record-Level Security determines which records users can access.
Example:
Sales Representative A:
Can view their own opportunities.
Sales Representative B:
Cannot view Representative A’s opportunities.
This helps protect sensitive business information.
Field-Level Security (FLS) controls access to individual fields within an object.
Even if a user can access a record, Field-Level Security determines whether they can:
Field-Level Security provides highly granular control over data visibility.
Not all users should see all information.
Example:
Employee Record:
Fields:
Most employees may view:
Only HR managers should view:
Field-Level Security makes this possible.
Field-Level Security operates independently of record access.
Example:
User can access:
Employee Record
But cannot view:
Salary Field
Result:
The Salary field is hidden.
This protects sensitive information while allowing access to other data.
Field-Level Security includes two primary settings.
Determines whether users can view the field.
Determines whether users can edit the field.
Administrators configure these settings through Profiles and Permission Sets.
Users can view the field.
Example:
Email Address
Users cannot see the field.
Example:
Salary Information
Hidden fields do not appear on:
This improves security and privacy.
Users can view but cannot modify field values.
Example:
Employee ID
Users may see:
EMP-1001But cannot edit it.
Benefits:
Read-only access is commonly used for system-generated fields.
A training institute manages student records.
Fields:
Access:
Can view:
Cannot view:
Can view:
Field-Level Security enforces these requirements.
Navigate to:
Setup → Object Manager
Select Object.
Example:
Student
Select:
Fields & Relationships
Choose the field.
Click:
Set Field-Level Security
Configure:
Save.
The changes take effect immediately.
Profiles control user permissions.
Examples:
Each Profile can define field access.
Example:
HR Profile:
Salary Field = Visible
Sales Profile:
Salary Field = Hidden
Profiles are a common method for managing Field-Level Security.
Permission Sets provide additional permissions without changing Profiles.
Example:
Temporary Finance Access
A user may receive permission to view financial fields through a Permission Set.
Benefits:
Modern Salesforce implementations often rely heavily on Permission Sets.
Field-Level Security affects reporting.
Example:
Salary Field:
Hidden
Result:
User cannot include the Salary field in reports.
This prevents unauthorized data exposure.
Field-Level Security also affects:
Hidden fields remain inaccessible across Salesforce.
This ensures consistent security enforcement.
Field-Level Security applies to:
If users cannot access a field through Salesforce:
They generally cannot access it through APIs either.
This helps secure integrations.
Many administrators confuse these concepts.
| Feature | Field-Level Security | Page Layout |
|---|---|---|
| Security Control | Yes | No |
| Hide Field Completely | Yes | No |
| Prevent API Access | Yes | No |
| Control Visibility | Yes | Partial |
| Enforce Security | Yes | No |
Field-Level Security should always be used for true security requirements.
| Feature | Field-Level Security | Record-Level Security |
|---|---|---|
| Controls Fields | Yes | No |
| Controls Records | No | Yes |
| Granularity | High | Medium |
| Security Focus | Individual Fields | Entire Records |
Both are essential components of Salesforce security.
Grant only necessary access.
Reduce Profile complexity.
Conduct periodic audits.
Apply Field-Level Security appropriately.
Verify permissions before deployment.
Support governance and compliance.
These practices strengthen Salesforce security.
Hide salary information.
Restrict revenue data.
Protect patient information.
Control scholarship visibility.
Limit commission access.
Field-Level Security supports many business scenarios.
Organizations should periodically review:
Regular audits help identify security gaps and maintain compliance.
Large organizations may have many Profiles and Permission Sets.
Security needs evolve over time.
Regulations may require stricter controls.
Balancing accessibility and security can be challenging.
Proper governance helps address these issues.
Understanding Data Security and Field-Level Security helps professionals:
Security knowledge is one of the most valuable skills for Salesforce professionals.
Data Security and Field-Level Security are essential components of the Salesforce security model. While Data Security protects organizational information through multiple layers of access control, Field-Level Security provides granular control over individual fields within records. By using Profiles, Permission Sets, Record-Level Security, and Field-Level Security together, organizations can protect sensitive information, maintain compliance, and ensure users have appropriate access to Salesforce data.
Data Security refers to the controls and processes used to protect Salesforce data from unauthorized access and modification.
Field-Level Security controls whether users can view or edit specific fields.
No. Hidden fields are not available in reports.
Field-Level Security provides actual security, while Page Layouts only affect field display.
It is configured through Profiles and Permission Sets.
It protects sensitive information and ensures appropriate access to business data.
Looking to learn more technologies and programming skills?