Introduction to Salesforce Security Model
Introduction to Salesforce Security Model – A Complete Beginner Guide
Salesforce is a powerful CRM platform used by thousands of businesses. One of the key reasons for its success is its robust security model that ensures data is safe, secure, and only visible to the right users.
In this guide, you'll learn everything about the Salesforce Security Model, step by step.
💡 What is the Salesforce Security Model?
The Salesforce Security Model is the framework that controls:
-
Who can access the system
-
What data they can see
-
What actions they can perform
The model is flexible, layered, and ensures data is protected at every level.
🔑 Types of Security in Salesforce
Salesforce provides two main types of security:
1. System Level Security
Controls access to Salesforce as a platform.
2. Data Level Security
Controls access to data (records, fields, objects).
Let’s understand both.
⚙️ System Level Security
🔹 1. Login Access
-
IP Restrictions: Limit user logins to trusted IP ranges.
-
Login Hours: Set working hours for users.
🔹 2. Password Policies
-
Set rules for password length, complexity, and expiration.
🔹 3. Two-Factor Authentication (2FA)
-
Adds an extra layer of security by requiring a code during login.
📊 Data Level Security
Salesforce gives fine-grained control using:
-
Object-level security
-
Field-level security
-
Record-level security
🔐 1. Object-Level Security
This controls what types of records (like Accounts, Contacts, Opportunities) a user can Create, Read, Edit, Delete.
✅ Managed through:
-
Profiles
-
Permission Sets
📋 2. Field-Level Security
Controls which fields within a record a user can see or edit.
🔧 Example:
-
A user can access the Contact record but not see the “Phone Number” field.
✅ Set via:
-
Field-Level Security in Profiles
-
Permission Sets
📄 3. Record-Level Security
Controls which specific records a user can access.
Salesforce uses several tools to manage this:
🏗️ Record-Level Access Tools
1. Organization-Wide Defaults (OWD)
Defines the default access for records.
Options:
-
Private (most restrictive)
-
Public Read Only
-
Public Read/Write
-
Controlled by Parent
Example:
If OWD for Account is Private, users can only see records they own unless shared.
2. Role Hierarchy
Gives access upward in the hierarchy.
📌 Example:
-
A manager can see records owned by their team.
-
Users higher in the role hierarchy inherit access.
3. Sharing Rules
Grant additional access to groups of users.
You can:
-
Share records based on criteria (Criteria-Based Sharing)
-
Share between roles (Role-Based Sharing)
Example:
Share all “High Priority” cases with the Support Manager role.
4. Manual Sharing
Let users manually share their records with others.
Best for:
-
One-off sharing needs
-
User-controlled access
5. Teams (Account/Opportunity/Case Teams)
Let multiple users collaborate on the same record with different access levels.
Example:
-
Sales Rep: Read/Write
-
Sales Assistant: Read Only
6. Apex Sharing
Programmatic way to share records using code (Apex).
Useful when:
-
Complex logic is needed
-
Standard sharing rules aren’t enough
👥 Profiles and Permission Sets – What's the Difference?
| Feature | Profile | Permission Set |
|---|---|---|
| Purpose | Base access | Additional access |
| Users | One profile per user | Multiple permission sets allowed |
| Example | Sales Profile | “Edit Reports” permission set |
🔍 Summary of Key Security Tools
| Tool | Controls | Level |
|---|---|---|
| Login IP/Hours | Login access | System |
| Profiles | Object & field access | Data |
| Permission Sets | Additional access | Data |
| OWD | Record access defaults | Record |
| Role Hierarchy | Upward access | Record |
| Sharing Rules | Group-level access | Record |
| Manual Sharing | One-off access | Record |
| Apex Sharing | Code-based access | Record |
✅ Best Practices for Salesforce Security
-
Always use least privilege (give only required access)
-
Regularly review roles and permissions
-
Use permission sets for flexibility
-
Enable 2FA for sensitive users
-
Avoid making everything public
-
Keep your OWD Private, then open access as needed
🎯 Final Words
The Salesforce Security Model is layered and flexible, ensuring that your organization’s data is well protected. By using the right combination of:
-
Profiles
-
Roles
-
Permission Sets
-
Sharing Rules
… you can keep your CRM secure and efficient.
Learn Salesforce Development Training Course
Comments
Post a Comment