Team Gamma: Tuesday Session - Meeting Summary This was an educational training session focused on Sales Process Configuration in Salesforce, led by Efe Igoni for the Team Gamma cohort. The session covered the foundational concepts and practical implementation of sales processes, record types, and opportunity management—essential components for managing customer relationships effectively. 🎯 Key Learning Objectives Covered The session addressed how to configure and implement sales processes that guide sales representatives through standardized stages when converting potential customers into actual buyers. Participants learned that sales processes are customizable based on organizational needs and vary depending on whether a company operates in B2B (business-to-business) or B2C (business-to-consumer) models. 📋 Main Topics Discussed Sales Process Fundamentals A sales process is the sequence of stages that sales representatives follow to move prospects through the sales pipeline. The stages shown in the opportunity record represent the sales process in action. 00:29 Efe explained that different business types require different sales processes—for example, selling human hair requires fewer stages than selling cars, which involve complex negotiations and multiple touchpoints. Creating a Sales Process To create a sales process, users must: 1. Navigate to Setup and search for "Sales Process" 2. Click New Sales Process and name it (e.g., "B2B Sales" or "B2C Sales") 3. Select opportunity stages from available values or create custom ones 4. Assign probability percentages to each stage based on likelihood of closing Opportunity Stages & Probability Participants learned how to create custom stages like: - Prospecting (10% probability) - Qualification (20% probability) - Needs Analysis (30% probability) - Payment (80% probability) - Delivery (90% probability) - Close Won/Close Lost (100% or 0%)

Team Delta: Wednesday Session Summary 📚 Overview This was an intensive beginner Salesforce training session covering foundational concepts, career opportunities, and hands-on platform setup. Godwin Mbah Mbah led discussions on Salesforce admin roles and LinkedIn strategy, while Jozzy guided everyone through Trailhead and Developer Org configuration. 🎯 What We Covered Salesforce Admin Role & Responsibilities Salesforce Administrators are the bridge between Salesforce and your business. Your key responsibilities include: - Creating and managing user accounts, profiles, and permissions - Customizing the platform using point-and-click tools - Ensuring data security so users only see what they need - Building automations and workflows - Creating reports and dashboards to track business metrics - Solving user issues and providing support Career Opportunities & Salary - Full-time Admin roles: $45,000–$70,000 annually - Contract work: Up to £500/day - Career growth: You can advance from Admin → Developer → Consultant → Architect (unlike other careers with limited growth) - Job demand: Recruiters actively search LinkedIn for Salesforce professionals Why Salesforce Matters Salesforce is industry-agnostic — every company (automotive, healthcare, education, finance, etc.) can use it. This means: - High demand across all sectors - Job security and flexibility - Ability to work remotely with multiple clients - Continuous innovation and new features 📱 LinkedIn Strategy LinkedIn is critical for your success. Here's what you need to do: 1. Create a LinkedIn profile if you don't have one 2. Connect with Godwin Mbah Mbah — don't just "follow" him, actually connect so he can boost your network 3. Follow Pathway to Salesforce company (you'll list this on your CV as your employer during certification) 4. Be active on LinkedIn — like posts, engage with content, and build visibility 5. Visibility = Opportunity — recruiters search LinkedIn for Salesforce professionals

Team Delta Session Summary - February 4, 2026 Duration: 3 hours (181 minutes) 🎯 Key Topics Covered 1. Welcome & Foundation Setting - Five new participants joined the session - Emphasis on commitment, continuous learning, and asking questions without fear - Importance of being "shameless" when stuck and using the community support system 2. Training Community Structure - Team Delta (Beginner level) - Wednesdays & Saturdays at 8 PM - Team Gamma (Intermediate) - Fridays at 8 PM - Team Alpha (Advanced) - Tuesdays - Sunday Q&A - General problem resolution - Timeline to certification: 8-12 weeks with consistent effort 3. What is Salesforce? Salesforce is the #1 CRM platform used to: - Monitor and manage customer relationships and activities - Automate business processes - Generate reports and analytics - Maintain accountability across teams - Support multiple business functions (Sales, Service, Marketing) 4. Role of a Salesforce Administrator Key responsibilities include: - User & Security Management - Setting up users, managing permissions, controlling access - Customization & Configuration - Building custom objects, automations, and workflows - Data Management - Importing, exporting, cleaning data, preventing duplicates - Reports & Analytics - Creating dashboards and KPI reports for stakeholders - User Support & Training - Training teams on new features and solutions - System Maintenance - Deploying updates and new features - Stakeholder Collaboration - Understanding business needs and implementing solutions 5. Essential Learning Platforms Pathway360 (Coach's Platform) - Beginner-friendly custom course - Best starting point for newcomers - Auto-completion tracking - Free access Trailhead (Salesforce Official) - Official Salesforce learning platform - Points and badges system - Hands-on exercises and playgrounds - Follow the specific Admin Trail Mix provided - Hiring managers often request your profile link

Team Alpha Salesforce Flows Training Summary Overview This was an in-depth training session for Team Alpha covering Salesforce Flows, focusing on practical implementation and real-world business scenarios1. Key Topics Covered 1. Flow Fundamentals - Introduction to different flow types: record-triggered flows, screen flows, scheduled flows, and auto-launch flows - Importance of decision elements for optimizing flow efficiency and avoiding Salesforce governor limits - Entry conditions vs. decision elements comparison 2. Record-Triggered Flows The team built and tested a record-triggered flow with the following features: - Triggered when opportunity records meet specific criteria (stage = "Proposal," amount ≥ £20,000, close date within 7 days) - Automatically creates follow-up tasks for opportunity owners - Sets task priority to "High" with due dates 2 days before opportunity close date - Prevents duplicate task creation using custom checkbox fields 3. Business Problem & Solution Problem: A UK-based software company was losing high-value opportunities (>£20,000) due to: - Manual follow-up tracking - No standardized reminder system - Lack of manager visibility into delayed deals Solution: Automated flow that: - Creates follow-up tasks automatically - Sends email alerts to managers if no activity occurs within 48 hours - Improves sales team productivity and revenue tracking 4. Technical Implementation Details - Custom Fields Created: - Decision Elements: Used to check if amount > £20,000 and if close date falls within 7 days - Update Record Elements: Mark opportunities to prevent duplicate task creation - Email Alerts: Organization-wide email addresses configured for manager notifications 5. Before-Save vs. After-Save Flows Demonstrated a simple before-save flow that automatically updates opportunity stage to "Closed Won" if amount exceeds £100,000 6. Mapping & Field Relationships - Linking tasks to opportunities using related record IDs - Assigning tasks to opportunity owners - Understanding lookup vs. master-detail relationships

Data Security Meeting Summary Overview This meeting covered Salesforce Data Security, focusing on the five layers of security and their practical implementation in a Salesforce organization. Key Topics Covered 1. Five Layers of Salesforce Security - Object-Level Security — Controls which objects users can access and what actions (create, read, edit, delete) they can perform - Field-Level Security — Restricts view/edit access to specific fields within objects - Record-Level Security — Controls access to individual records - Organization-Level Security — Governs login hours, IP ranges, and password policies across the org - Org-Wide Default (OWD) — Sets baseline record-level access (private, public read-only, public read/write) 2. Object-Level Security Implementation - Configured through user Profiles - Controls permissions for create, read, edit, and delete operations on objects - When permissions are restricted, users cannot perform those actions - Permission Sets are used to grant additional privileges without modifying the base profile 3. Field-Level Security - Controls visibility and editability of specific fields - Two permissions: Read (view) and Edit - If read access is unchecked, the field is completely hidden and cannot be edited - Implemented at the profile level 4. Organization-Level Security - Login Hours — Restricts access to specific times (e.g., 9 AM - 4 PM) - IP Login Ranges — Limits access to specific company locations/networks - Password Policy — Enforces password expiration, complexity, length, and history requirements - Login Lockout — Limits failed login attempts and lockout duration 5. Org-Wide Default (OWD) & Record-Level Access - Private — Users only see their own records - Public Read-Only — Users can view all records but cannot edit - Public Read/Write — Users can view and edit all records - OWD is the baseline; other mechanisms (role hierarchy, sharing rules, manual sharing) can grant additional access