4d (edited) • 🎖️CHALLENGES /ASSIGNMENTS HUB
3 MEGA REAL PORTFOLIO PROJECTS TO TEST YOUR KNOWLEDGE ON DUPLICATE RULES, DATA MODEL AND DATA SECURITY: 3 GROUPS
THIS IS FOR STUDENTS WHO HAVE GOTTEN TO THIS LEVEL:
🏗️ GROUP A – PROJECT TITLE: CleanHire CRM Overhaul
Company: PrecisionHire UK Ltd – London-based tech recruitment agency
Sector: Recruitment & Staffing
Focus Areas: Data Security • Data Model • Duplicate Rules
🔍 Business Scenario:
PrecisionHire helps tech startups find top-tier developers. Their sales and talent teams use Salesforce to manage Clients, Vacancies, and Candidates — but things are breaking fast.
Here’s what’s wrong:
❌ Everyone uses the same profile — Talent team can see sensitive client billing data
❌ All Candidates and Vacancies are dumped under Accounts and Opportunities
❌ Duplicate Candidates are flooding the system — same names, emails, or just slightly different spellings
📉 Management is struggling to track who placed which candidate in which vacancy, and reporting is unreliable
✅ Your Admin Tasks:
🔹 Data Model:
Create 3 Custom Objects:
Candidate__c
Vacancy__c
Placement__c (junction object linking Candidate and Vacancy)
Add necessary fields like:
Candidate: Full Name, Email, Skillset, Recruiter
Vacancy: Title, Client (lookup to Account), Status
Placement: Candidate, Vacancy, Start Date, Status
Use Lookup or Master-Detail relationships appropriately
Ensure you can run reports showing Vacancies filled per Client and Candidate status
🔹 Data Security:
Talent Team should ONLY access Candidate and Placement data
Sales Team should ONLY see Vacancies and Client Accounts
Billing Team should only view Placement fees (hide from Talent team)
Use Profiles, Permission Sets, Role Hierarchy, and Field-Level Security
Set Org-Wide Defaults properly and apply sharing rules where needed
🔹 Duplicate Rules:
Prevent duplicate Candidate records using Email + Full Name
Warn users on similar Vacancies using Title + Account
Block exact matches on Placement records (same candidate, same vacancy)
🏢 GROUP B – PROJECT TITLE: BuildPro CRM Revamp
Company: BuildPro Solutions – Manchester-based commercial construction firm
Sector: Construction Project Management
Focus Areas: Data Security • Data Model • Duplicate Rules
🔍 Business Scenario:
BuildPro handles dozens of construction projects, each linked to different contractors and site engineers. Their Salesforce org is cluttered — nothing is structured, data is duplicated, and roles are unclear.
Problems they’re facing:
📁 Site Engineers are seeing financial contracts
🧱 There’s no object tracking for Buildings, Contracts, or Site Visits
⚠️ Multiple users are logging the same site visit or creating the same project twice
📊 Senior Managers can’t get clean reports by contractor or region
✅ Your Admin Tasks:
🔹 Data Model:
Create custom objects for:
Building__c
Contract__c
Site_Visit__c
Fields to include:
Building: Name, Region, Status
Contract: Amount, Contractor (lookup to Account), Building
Site Visit: Date, Notes, Linked Contract, Assigned Engineer
Set up correct relationships
Ensure reports can show Contracts by Building, and Visits per Contractor
🔹 Data Security:
Site Engineers should only see Site Visits assigned to them
Finance should only see Contract amounts
Managers should see all records within their assigned region
Use Roles, Profiles, Field-Level Security, and Org-Wide Defaults
🔹 Duplicate Rules:
Prevent duplicate Buildings (match on Name + Region)
Warn users when logging Site Visits on the same date, same contract
Block exact duplicates on Contracts with same Building + Contractor
🎓 GROUP C – PROJECT TITLE: EdSpark360 – Academic Data Rebuild
Company: EdSpark Academy – Birmingham-based online education provider
Sector: EdTech / Online Learning
Focus Areas: Data Security • Data Model • Duplicate Rules
🔍 Business Scenario:
EdSpark offers online training programs to schools and corporate clients. Their Salesforce org is overloaded with duplicate student entries, unstructured course records, and exposed financial info.
Here’s the chaos:
📚 Students are entered 2-3 times with different emails or misspelled names
🧾 Instructors can see invoices and partner pricing
📂 There's no structure for Courses, Enrollments, and Students
❌ Support team can edit sensitive learning outcomes and attendance
✅ Your Admin Tasks:
🔹 Data Model:
Create 3 Custom Objects:
Course__c
Student__c
Enrollment__c (junction object)
Fields to include:
Course: Title, Duration, Type
Student: Full Name, Email, School/Org
Enrollment: Student, Course, Start Date, Progress %
Set correct relationships: One Course has many Enrollments, One Student can enroll in many Courses
Ensure you can report on progress by Course, Student, or School
🔹 Data Security:
Instructors can see student progress, but NOT pricing or financials
Finance can view Course pricing, but not student names
Support can only update student progress, not enrollment dates or financials
Use Field-Level Security, Profiles, Permission Sets, and Role Hierarchy
🔹 Duplicate Rules:
Block duplicate Students using Full Name + Email
Warn on Courses with same title + type
Prevent duplicate Enrollments with same Student + Course combination
📝 Instructions for All Groups:
Work together using your dev orgs
Decide how you'll implement each requirement
Test with different users to simulate real-life access
Prepare a 5-minute demo presentation showing your data model, security setup, and duplicate rule test
CHOOSE YOUR GROUP AND GET TO WORK GUYZ:
WORK IN YOUR GROUPS COLLAPORATIVELY
DEMO ON THE NEXT CLASS, ON SATURDAY
GROUP A
GROUP B
GROUP C
8
21 comments
3 MEGA REAL PORTFOLIO PROJECTS TO TEST YOUR KNOWLEDGE ON DUPLICATE RULES, DATA MODEL AND DATA SECURITY: 3 GROUPS
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)
1
+222
2
+195
3
+137
4
+77
5
+72
Powered by