🧶MASSIVE SALESFORCE PROJECT TO BE DONE BY INSTRUCTOR IN CLASS FOR STUDENTS TO LEARN AND ASK QUESTIONS: TEAM GAMMA CLASS TONIGHT
Asda Salesforce Admin Project, Users, Security, Record Types, Sales Process and Path
Project Type
This project will be built live in class by the instructor.
Students are expected to follow along during the session and then complete the same project inside their own Salesforce Developer Org.
You may collaborate with others, but every student must complete the project personally and be able to explain their own setup.
šŸ¢ Company Background
You have just joined Asda as a Junior Salesforce Admin.
Asda wants to improve how different internal teams manage customer related work inside Salesforce. The business wants better structure, better access control, and a clearer sales process for business customer opportunities.
Asda has different teams using Salesforce:
• Store Sales Team• Business Sales Team• Customer Support Team• Sales Managers• Regional Managers
At the moment, everyone is using Salesforce in a very general way. There is poor structure around user access, opportunity stages, and how different teams should manage their work.
āš ļø Business Problem
Asda is facing the following issues:
• All users have similar access even though they do different jobs• Sales users are confused about which opportunity process to follow• Business sales deals are more complex than normal store related deals• Managers want visibility into their team’s records• Some users have access they do not need• There is no clear Path guiding users through sales stages• Leadership wants Salesforce to reflect how the business actually works
šŸŽÆ Business Goal
Asda wants Salesforce to support the business properly by introducing:
• Clear user setup• Better access control• Permission Sets for additional access• Record Types for different sales processes• Sales Processes with clear stages• Sales Path to guide users through each stage
🧠 Your Role as the Salesforce Admin
As the Salesforce Admin, your job is to configure Salesforce so Asda users have the right access, follow the right process, and understand what to do at each stage of the sales journey.
āœ… What You Must Build
1. Create Users
Create the following sample users in your Developer Org if your org allows it. If you cannot create all users, create at least the names as test users or document how you would create them.
User 1
Name: Sarah GreenRole: Store Sales RepTeam: Store Sales Team
User 2
Name: James PatelRole: Business Sales RepTeam: Business Sales Team
User 3
Name: Aisha KhanRole: Customer Support AgentTeam: Customer Support Team
User 4
Name: David MillerRole: Sales ManagerTeam: Sales Management
User 5
Name: Helen RobertsRole: Regional ManagerTeam: Regional Leadership
2. Create Roles
Create a simple role structure.
Role 1
Role Name: Regional Manager
Role 2
Role Name: Sales ManagerReports to: Regional Manager
Role 3
Role Name: Store Sales RepReports to: Sales Manager
Role 4
Role Name: Business Sales RepReports to: Sales Manager
Role 5
Role Name: Customer Support AgentReports to: Sales Manager
3. Assign Users to Roles
Assign the sample users to the correct roles.
• Helen Roberts, Regional Manager• David Miller, Sales Manager• Sarah Green, Store Sales Rep• James Patel, Business Sales Rep• Aisha Khan, Customer Support Agent
4. Create Permission Sets
Create the following Permission Sets.
Permission Set 1
Name: Opportunity Advanced Access
Purpose:For users who need extra access to manage Opportunities.
Give this Permission Set access to create, read, and edit Opportunities.
Assign it to:• James Patel• David Miller
Permission Set 2
Name: Case Support Access
Purpose:For users who need access to customer support work.
Give this Permission Set access to read, create, and edit Cases.
Assign it to:• Aisha Khan• David Miller
5. Create a Permission Set Group
Create one Permission Set Group.
Permission Set Group Name
Asda Sales and Support Access Group
Add these Permission Sets into the group:
• Opportunity Advanced Access• Case Support Access
Assign the Permission Set Group to:
• David Miller
Purpose:David Miller is the Sales Manager, so he needs broader visibility and access across both sales and support activity.
šŸ” Data Security Requirement
Configure access so that:
• Sales reps can work with their own Opportunities• Sales Managers can view team related sales activity• Customer Support Agents can work with Cases• Users should not receive access they do not need• Extra access should be given through Permission Sets where possible
Students should be ready to explain why Profiles, Roles, Permission Sets, and Permission Set Groups are used differently.
šŸ’¼ Sales Process Requirement
Asda wants two different Opportunity processes.
6. Create Two Opportunity Record Types
Record Type 1
Name: Store Partnership Opportunity
Purpose:Used for smaller local store partnership deals.
Example:A local supplier wants to partner with an Asda store for local product placement.
Record Type 2
Name: Business Account Opportunity
Purpose:Used for larger business deals with corporate suppliers, logistics partners, or national vendors.
Example:A national supplier wants to sell products across multiple Asda locations.
7. Create Two Sales Processes
Each Record Type should have its own Sales Process.
Sales Process 1
Name
Store Partnership Sales Process
Use these stages:
• Prospecting• Needs Review• Proposal Shared• Store Approval• Closed Won• Closed Lost
Purpose:This process is shorter because store partnership deals are smaller and easier to approve.
Sales Process 2
Name
Business Account Sales Process
Use these stages:
• Prospecting• Discovery Meeting• Business Needs Analysis• Proposal Shared• Commercial Review• Contract Negotiation• Closed Won• Closed Lost
Purpose:This process is longer because business account deals require more review, pricing discussion, and approval.
šŸ›¤ļø Path Requirement
8. Create Sales Path for Each Record Type
Create a Path for the Opportunity object that helps users understand what to do at each stage.
Path 1
Name
Store Partnership Opportunity Path
Use this for:Store Partnership Opportunity
Add guidance for these stages:
Prospecting
Confirm the local supplier details and understand the opportunity.
Needs Review
Identify what the supplier wants and whether the store can support it.
Proposal Shared
Send partnership details and next steps.
Store Approval
Confirm internal approval from the store manager.
Closed Won
Confirm partnership agreement.
Closed Lost
Record why the deal did not move forward.
Path 2
Name
Business Account Opportunity Path
Use this for:Business Account Opportunity
Add guidance for these stages:
Prospecting
Identify the business account and key decision makers.
Discovery Meeting
Understand the supplier’s goals, product type, and national opportunity.
Business Needs Analysis
Review requirements, pricing expectations, delivery needs, and commercial fit.
Proposal Shared
Send full proposal to the business contact.
Commercial Review
Review pricing, margins, and internal approvals.
Contract Negotiation
Finalize terms before closing.
Closed Won
Confirm signed agreement and next steps.
Closed Lost
Capture the reason the deal was lost.
šŸ“Š Sample Records to Create
Create at least 4 sample Opportunities.
Opportunity 1
Name: Local Bakery PartnershipRecord Type: Store Partnership OpportunityStage: Needs ReviewAmount: £8,000
Opportunity 2
Name: Manchester Fresh Produce SupplierRecord Type: Store Partnership OpportunityStage: Store ApprovalAmount: £15,000
Opportunity 3
Name: National Cleaning Products SupplierRecord Type: Business Account OpportunityStage: Commercial ReviewAmount: £120,000
Opportunity 4
Name: UK Logistics Partner ExpansionRecord Type: Business Account OpportunityStage: Contract NegotiationAmount: £250,000
šŸ“Œ What Students Must Demonstrate
During the class or after completing the project, each student should be able to show:
• Users created or documented• Roles created and assigned• Permission Sets created• Permission Set Group created• Opportunity Record Types created• Sales Processes created• Sales Path configured• Sample Opportunities created• Explanation of why each setup was needed
šŸŽ¤ Presentation Expectations
When presenting, students should explain:
1. The Business Problem
What was Asda struggling with?
2. User Management
Which users and roles were created?
3. Data Security
How does the setup control access?
4. Permission Sets
Why were Permission Sets used?
5. Permission Set Group
Why was a Permission Set Group useful for the manager?
6. Record Types
Why does Asda need two Opportunity Record Types?
7. Sales Process and Path
How does each Path guide users through the correct sales journey?
8. Business Impact
How does this setup help Asda work better?
ā³ Deadline
This will be built live in class by the instructor.
After the session, every student must complete it in their own Developer Org.
Students should be ready to present or explain their work in the next class.
Final Note
This project is designed to test your understanding of real Admin work.
You are not just clicking buttons.
You are learning how Salesforce supports users, access, processes, and business structure.
Build it carefully, understand it properly, and be ready to explain your decisions.
21
6 comments
Godwin Mbah
7
🧶MASSIVE SALESFORCE PROJECT TO BE DONE BY INSTRUCTOR IN CLASS FOR STUDENTS TO LEARN AND ASK QUESTIONS: TEAM GAMMA CLASS TONIGHT
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