#Salesforce #SalesforceSecurity
How would you design a Salesforce security model for Sales, Marketing, and Support teams so that each team can access the records and fields required for its job without exposing confidential information?
Hi @SAITEJA B Good question! In real Salesforce projects, security should follow the Principle of Least Privilege, meaning users should access only the data required for their jobs.
1. Recommended Security Model
- Profiles: Assign minimum permissions based on user responsibilities.
- Permission Sets: Provide additional object, field, and system permissions based on department needs.
- OWD: Set sensitive objects to Private by default.
- Role Hierarchy: Allow managers to access their team's records where required.
- Sharing Rules: Share selected records between departments based on business requirements.
- Field-Level Security: Restrict confidential fields such as Salary, Revenue, and Customer Financial Details.
2. Department-Wise Example
- Sales Team: Access Leads, Accounts, Contacts, and Opportunities.
- Marketing Team: Access Campaigns and required Lead information.
- Support Team: Access Cases and relevant customer information.
3. Important Best Practices
- Use Permission Set Groups for department-specific access.
- Avoid unnecessary View All and Modify All permissions.
- Use Sharing Rules to provide additional record access.
- Test access using different user accounts.
- Review permissions regularly.
4. Official Salesforce Resources
Create three test users representing Sales, Marketing, and Support. Configure OWD, Permission Sets, Roles, and Sharing Rules, then verify what each user can access.
Key Point:
Start with minimum access and provide additional permissions only when required.
Hope this helps! Venkat Yadav | SFDCINDIA