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

Good Morning All, I hereby announce the winners of the November Challenge, thank you all for taking part, we’ve loved reading your posts/ positive news and what you’ve been learning. 1ST PLACE @Divine Lantum £50 luxury gift of your choice 2ND PLACE @Sunday Odebiyi £40 Uber Eats voucher 3RD PLACE @Oluwatosin Adewoyin £20 gift voucher

🏢 COMPANY BACKGROUND: You’ve just been hired as a Junior Admin for SwiftMoves Ltd, a UK-based logistics company helping small businesses move packages and equipment across the country. The business is growing fast, and users are struggling to enter data correctly and quickly. You’ve been asked to create simple Screen Flows to guide users through data entry — no more messy record creation! This is your first Flow project, and you’ll build 3 beginner-level Screen Flows, one each for Leads, Accounts, and Opportunities. 🔧 YOUR TASK: Create 3 Screen Flows, each on a different object. These should all: - Use Screen Elements for guided input - Save the data to the relevant object - Include basic input validation (e.g., required fields) - Be beginner-friendly and clean 🧩 FLOW 1 – Lead Capture Flow Business Use Case:The Sales team wants a quick way to log new leads during phone calls. Requirements: - Create a Screen Flow on the Lead object - Fields to include: - First Name - Last Name - Company - Email - Lead Source (Dropdown picklist) - After the user enters details, save the record and show a confirmation screen - Make Email a required field 🧩 FLOW 2 – New Business Account Creation Business Use Case:Admins are creating business accounts manually. They want a flow that captures only key fields. Requirements: - Create a Screen Flow on the Account object - Fields to include: - Account Name - Industry (Dropdown) - Type (Customer, Partner, Prospect) - Website (Optional) - After submission, show a screen that says: “Account [Name] has been created!” - Account Name and Type should be required 🧩 FLOW 3 – Opportunity Quick Entry Business Use Case:Sales reps want a simplified form to create an Opportunity from anywhere — they don’t want to see the full layout. Requirements: - Create a Screen Flow on the Opportunity object - Fields to include: - Opportunity Name - Close Date - Stage (Dropdown) - Amount - Related Account (Lookup)

Hey everyone, a quick update, we appologise won’t be launching Pathway AI today as planned. We’re finalising a few technical adjustments with the AI Agents to make sure everything runs smoothly once it’s live. We just want to deliver the best version possible, so stay tuned, keep calm and get ready to be blown away by Pathway AI. We’ll announce the new launch date later this week, so stay close. This short wait will be worth it. Kind regards Godwin Mbah