📍 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)

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

A UK-based property management company Property AI, is scaling fast, and their Salesforce is a mess. Here’s what’s going on: 🏢 Every Building is being tracked as an Account 📋 Each Maintenance Request is logged as a Note — no real tracking 👷‍♂️ Engineers and Property Managers all share the same Profile 🧾 Finance wants to assign specific Tasks to Property Managers, but there’s no link between records 📉 Management can’t generate reports showing open tasks per building or who’s responsible You’re the Admin. They’ve asked you to: ✅ Redesign the data model to reflect how Buildings, Requests, and Users interact ✅ Set up users with different levels of access based on their role in the org ✅ Track who is assigned to each building and each task ✅ Make sure reports show assigned work and progress across the portfolio What’s your BEST next move? Choose the correct option 👇 Drop your answer and reasoning in the comments, let’s see who really understands data model and user setup 🧠 #WhoCanFixThis #DataModel #UserManagement #SalesforceAdmin #PathwayToSalesforce #ThinkLikeAnAdmin

A UK-based healthcare company is losing trust in their Salesforce reports. Here’s what’s happening: 📥 Duplicate Leads and Contacts are being created by different reps 📊 Revenue is being double-counted in dashboards 🤦 Management can’t tell which pipeline data is accurate You’re the Admin. The company wants: ✅ Clean, accurate reports ✅ A way to warn or block users before duplicates are saved ✅ A lightweight solution that doesn’t slow the sales team down What’s your BEST move? 👇 Drop your answer in the comments, and explain your reasoning. Let’s see who’s thinking clearly under pressure 😏 #WhoCanFixThis #DataIntegrity #SalesforceAdmin #DuplicateData

Tonight’s class = BUILD TIME. No slides. No lectures. Just real admin work. 🏢 THE STORY: You’ve just joined NexaTech, a fast-growing cybersecurity company in London. The sales team is messing up the CRM — leaving fields blank, entering fake data, and rushing deals. Your manager just gave you ONE task: Put rules in place that force the reps to follow our business process. No more messy records.” -💼 YOUR JOB TONIGHT: Create 5 validation rules that solve these real problems inside the org. You’ll work across the Opportunity, Account, and Contact objects. Use your developer org. No help. Just you, your logic, and Trailhead. 🧩 YOUR 5 TASKS: 🔹 1. Stop reps from closing deals without an amount If the Opportunity is marked as Closed Won, there must be an Amount entered. --- 🔹 2. Block Business Accounts without a website If the Account type is Business, the Website field must be filled before saving. --- 🔹 3. Enforce UK phone number format On the Contact object, phone numbers must start with the UK code (e.g. +44). --- 🔹 4. Block Opportunities with no Close Date Sales reps should NOT be able to create or save an Opportunity without setting a Close Date --- 🔹 5. Make sure email addresses look like emails * On the Contact object, email fields must contain an `@` — no more fake entries. --- 🧠 YOUR GOAL: * Create ALL 5 validation rules * Make sure the error messages are clear * Take screenshots to prove your work (Rule + Error Message in action) * Upload in the group before the next class * Be ready to explain your logic live! --- 📚 RESOURCES FOR RESEARCH: * 👉 [Validation Rules – Trailhead Module](https://trailhead.salesforce.com/content/learn/modules/validation_rules/validation_rules_intro) * 👉 [Formula Functions Reference](https://help.salesforce.com/s/articleView?id=sf.customize_functions.htm&type=5)