💼FULL PORTFOLIO PROJECT TITLE: SecureHire360 – Data Model & Security Overhaul for a UK Recruitment Firm

20d (edited) • 🎖️CHALLENGES /ASSIGNMENTS HUB

📍 Company: SecureHire Ltd

A recruitment agency based in Manchester that connects tech professionals to contract and permanent jobs across the UK.

🧠 PROJECT BACKGROUND:

SecureHire has recently migrated from spreadsheets to Salesforce. The company is growing fast, and leadership has asked YOU, their new Salesforce Admin, to build a secure, scalable data model that matches how the business actually works.

Right now, everything is being dumped into the Account and Opportunity objects, and data is being viewed and edited by the wrong people.

Leadership’s biggest concern?

Recruiters are seeing salary info they shouldn’t
Sales reps are editing candidates they don’t manage
Managers want reports by industry, recruiter, and region
Finance wants visibility into payments only
Data structure is messy, reporting is unreliable, and data access is out of control

🔧 YOUR TASK (As the Admin):

You are required to design and implement a proper Data Model and apply security controls to protect sensitive data and clean up the chaos.

📊DATA MODEL – OBJECTS TO CREATE:

🔹Custom Object 1: Candidate__c

Stores individual candidate information

Fields to Create:

Full Name (Text)
Email (Email)
Phone (Phone)
Current Role (Text)
Expected Salary (Currency)
Availability Date (Date)
Assigned Recruiter (Lookup to User)
Region (Picklist – North, South, Midlands, Scotland, Remote)

🔹Custom Object 2: Job_Position__c

Represents open job roles from client companies

Fields to Create:

Job Title (Text)
Department (Picklist)
Salary Range (Currency)
Employment Type (Picklist – Contract, Permanent)
Hiring Manager (Lookup to Contact)
Status (Picklist – Open, Interviewing, Closed)
Linked Account (Lookup to Account)

🔹Custom Object 3: Placement__c

Represents a match between a candidate and a job

Fields to Create:

Candidate (Lookup to Candidate__c)
Job Position (Lookup to Job_Position__c)
Start Date (Date)
End Date (Date)
Placement Status (Picklist – Interviewing, Offered, Accepted, Rejected)
Recruiter (Lookup to User)

🎯 Relationships:

One Job_Position__c can have many Placements__c
One Candidate__c can be linked to many Placements__c
Recruiters are assigned to Candidates
Hiring Managers are Contacts related to Accounts

🔐DATA SECURITY REQUIREMENTS:

Your job is to enforce access control so that each user type only sees and does what they are allowed to.

👩🏽‍💼 Recruiters:

Can view and edit only the candidates assigned to them
Cannot see salary info for jobs they’re not managing
Can only access job roles linked to Accounts they own

🧑🏽‍💼 Sales Team:

Can see all Job Positions
Cannot edit Candidate records
Can view Placements, but cannot delete them

📊 Finance Team:

Can view all Placements
Can only see salary-related fields, nothing else
Should not be able to create or edit any records

👨🏽‍💼 Regional Managers:

Can view everything in their region (based on Region field on Candidate__c)
Can run reports by recruiter, department, and region
Can’t edit Placement data

🛠️ WHAT YOU NEED TO IMPLEMENT:

Create all required custom objects and fields listed above
Set up the correct relationships (Lookups and Master-Details where needed)
Configure Org-Wide Defaults to secure records
Use Roles, Profiles, and Permission Sets to implement access controls
(Optional) Use Sharing Rules for regional manager visibility
Prepare test users and try logging in with each role to verify access

📷 DELIVERABLES:

Screenshot of each custom object with fields visible
Screenshot of Role Hierarchy and sharing settings
Evidence that the right users have the right level of access (e.g., recruiter can’t see another recruiter’s candidate)
Bonus: Create a custom report showing placements by region

🧠 HINTS & REMINDERS:

Don’t forget to test each scenario by logging in as a different user
Use Profile and Permission Sets smartly — don’t overload Profiles
Think about OWD settings before creating Sharing Rules
Be thoughtful about field-level security (e.g., hide Expected Salary from Sales Team)

🔗 OPTIONAL RESOURCES (For Study):

🏁 FINAL NOTE:

This is a portfolio-grade project, realistic, challenging, and 100% Admin territory.

You’ll present your solution in the next class and explain your choices like a real pro.

#WeekendProject #DataModel #DataSecurity #PathwayToSalesforce #SalesforceAdmin

19 comments

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)

+212

+188

+137

+73

+70