🏆 TODAY’s CLASS TIME IS FOR THIS, NO CLASS. USE THE TIME TO COMPLETE THIS PROJECT: Portfolio Project End to End User Management and Data Security Implementation
🏢 Business Context
You are the Salesforce Administrator supporting Tesco UK.
Salesforce Sales Cloud is used to manage Accounts and Opportunities for large business customers and strategic suppliers. Multiple teams access Salesforce, and sensitive revenue data must be protected while still allowing sales teams to work efficiently.
Your task is to design and implement proper user management and data security, exactly how it would be done in a real organisation.
This project focuses strictly on
• Users
• Profiles
• Roles
• Record visibility
• Field level security
🎯 Project Objective
By completing this project, you will demonstrate that you can
• Control what users can do
• Control what records users can see
• Protect sensitive financial data
• Test and validate security behaviour
This is a portfolio grade project and will be reviewed and demoed.
👥 Teams Using Salesforce
Sales Team
Finance Team
Management
👤 Users In Scope
Use the limited Salesforce licenses available in your Developer Org.
Your implementation must support the following roles
• Sales Executive
• Sales Manager
• Finance User
• Salesforce Administrator
📊 Objects In Scope
You will work only with standard Sales Cloud objects
• Account
• Opportunity
No custom objects.
No record types.
🧱 Fields You Must Create on Opportunity
Create the following custom fields on the Opportunity object.
Finance Sensitive Fields
These fields must be visible only to Finance Users and the Salesforce Admin.
• Forecasted Margin Percentage, Number
• Approved Discount Amount, Currency
• Finance Internal Notes, Long Text Area
Sales Only Fields
These fields must be visible to Sales Users and the Salesforce Admin, but hidden from Finance.
• Sales Strategy Notes, Long Text Area
• Competitor Involved, Checkbox
🔐 Security Requirements
Sales Executive
• Can create and edit their own Accounts and Opportunities
• Can only see Opportunities they own
• Cannot see Opportunities owned by other Sales Executives
• Cannot see any Finance Sensitive fields
• Can see Sales Only fields
Sales Manager
• Can see all Accounts and Opportunities owned by their Sales team
• Can edit Opportunities owned by their team
• Cannot see Finance Sensitive fields
• Can see Sales Only fields
Finance User
• Can see all Opportunities across the organisation
• Has read only access to Opportunities
• Can see Finance Sensitive fields
• Cannot see Sales Only fields
• Cannot create or edit Accounts or Opportunities
Salesforce Administrator
• Full access for configuration and testing
🔒 Record Visibility Expectations
Your configuration must ensure that
• Sales Executives only see their own records
• Sales Managers see records owned by their team
• Finance Users see all Opportunities but cannot edit them
This must be achieved using
• Org Wide Defaults
• Role Hierarchy
No sharing rules are required unless you believe they are necessary and can justify them during demo.
🧪 Testing Requirements
You must prove security behaviour by logging in as each user and capturing evidence that shows
• Which records are visible
• Which records are hidden
• Which fields are visible
• Which fields are hidden
At least one screenshot must show a user attempting to access data they are not allowed to see.
📸 Submission Requirements
Submit one PDF document containing screenshots of
• User list
• Profiles and object permissions
• Role Hierarchy
• Org Wide Defaults
• Opportunity field creation
• Field level security for each custom field
• Login tests for each user role
• Proof of restricted access
Name the file
Firstname Lastname, Sales Cloud User Management and Data Security Project
Upload the PDF under the project post.
🎤 Demo Expectations
You must be able to explain
• Why you chose the Org Wide Defaults you selected
• How Role Hierarchy affects visibility
• How Field Level Security protects sensitive data
• What would break if security was not designed this way
This mirrors real Salesforce Admin interview scenarios.
⏰ Class Instruction
Use today’s 8 p.m. class time to build and test this project.
This is execution time, not teaching time.
This project is designed to show whether you can think and build like a real Salesforce Administrator.
17
62 comments
Godwin Mbah
7
🏆 TODAY’s CLASS TIME IS FOR THIS, NO CLASS. USE THE TIME TO COMPLETE THIS PROJECT: Portfolio Project End to End User Management and Data Security Implementation
Pathway To Salesforce (PTS)
skool.com/pathway-to-salesforce
A community to help you transition into tech, master Salesforce skills, and unlock career opportunities with hands-on learning and real-world support.
Leaderboard (30-day)
Powered by