Data Security Meeting Summary
Overview
This meeting covered Salesforce Data Security, focusing on the five layers of security and their practical implementation in a Salesforce organization.
Key Topics Covered
1. Five Layers of Salesforce Security
- Object-Level Security โ Controls which objects users can access and what actions (create, read, edit, delete) they can perform
- Field-Level Security โ Restricts view/edit access to specific fields within objects
- Record-Level Security โ Controls access to individual records
- Organization-Level Security โ Governs login hours, IP ranges, and password policies across the org
- Org-Wide Default (OWD) โ Sets baseline record-level access (private, public read-only, public read/write)
2. Object-Level Security Implementation
- Configured through user Profiles
- Controls permissions for create, read, edit, and delete operations on objects
- When permissions are restricted, users cannot perform those actions
- Permission Sets are used to grant additional privileges without modifying the base profile
3. Field-Level Security
- Controls visibility and editability of specific fields
- Two permissions: Read (view) and Edit
- If read access is unchecked, the field is completely hidden and cannot be edited
- Implemented at the profile level
4. Organization-Level Security
- Login Hours โ Restricts access to specific times (e.g., 9 AM - 4 PM)
- IP Login Ranges โ Limits access to specific company locations/networks
- Password Policy โ Enforces password expiration, complexity, length, and history requirements
- Login Lockout โ Limits failed login attempts and lockout duration
5. Org-Wide Default (OWD) & Record-Level Access
- Private โ Users only see their own records
- Public Read-Only โ Users can view all records but cannot edit
- Public Read/Write โ Users can view and edit all records
- OWD is the baseline; other mechanisms (role hierarchy, sharing rules, manual sharing) can grant additional access
6. Role Hierarchy
- Establishes organizational structure with superior-subordinate relationships
- Superiors automatically see all records created by their subordinates
- Can be customized with different role names and levels
- Users are assigned to roles to define their position in the hierarchy
Important Concepts
โ
Login Access Policy โ Must be enabled for admins to log in as other users for testing purposes
โ
Test Users โ Create standard profile test users to validate permission configurations
โ
Practice is Essential โ Understanding these concepts requires hands-on practice in a sandbox/dev org
Next Session
The instructor will cover Sharing Rules and Manual Sharing, which are additional mechanisms to grant record-level access beyond the baseline OWD settings.
Action Items
- Practice implementing all five security layers using test users
- Complete assignments on Trailhead and the training platform
- Prepare questions for the Q&A session on Sunday