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

🚀 Start Your Salesforce Journey Hi everyone! If you’re new to Salesforce, use the links below to get started. These resources are free and beginner-friendly. 1️⃣ Trailhead (Sign Up First) This is Salesforce’s learning platform.👉 Trailhead Sign-Up:[PASTE LINK HERE] 2️⃣ Salesforce Developer Account Gives you a free practice environment.👉 Developer Account:[PASTE LINK HERE] 3️⃣ Pathway to Salesforce Course A guided course made for beginners.👉 Pathway to Salesforce: Salesforce Fundamentals – (1/8) – Pathway To Salesforce 4️⃣ Trailhead Trail Mix A learning playlist you should complete.👉 Trail Mix:[PASTE LINK HERE]

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

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

GENERAL Q&A 4 - Meeting Summary Date: February 1, 2026 Duration: 180 minutes Key Topics Covered: 1. Salesforce List Views Fundamentals 1 List views are customizable filters that help sales representatives quickly access filtered records (e.g., open opportunities, closed deals). They're essential for improving user efficiency and can be configured with specific visibility permissions (only you, all users, or specific groups). 2. Creating Account List Views - Practical Exercise 1 Students learned step-by-step how to create a unique account list view filtered by industries (Energy and Biotech) with visibility set to "All Users." A common mistake to avoid: filtering by Account Name instead of Industry field. 3. Configuring List View Filters & Adding Fields 1 Proper filter configuration is crucial. Students practiced adding and reordering fields in list views and learned how to visualize records by category using charts for KPIs (Key Performance Indicators). 4. Trailhead Challenges & Org Management 1 Critical lesson: Always use the correct connected Trailhead Playground org when completing challenges. Many students were attempting exercises in personal Developer orgs instead of the linked Trailhead org, causing verification failures. Solution: Always click "Launch" to open the correct org before starting exercises. 5. Trailhead Playground vs Developer Org 1 - Trailhead Playground: For completing Trailhead exercises (automatically connected) - Developer Org: For personal projects and Pathway exercises - Keep these separate to avoid confusion and verification errors - Both are technically developer orgs, but serve different purposes 6. Front End vs Back End Usage 1 - Back End (Setup): Where admins configure objects, fields, security, and automation - Front End: Where users interact with records and where admins test configurations - Admins spend ~70% of time in the back end, ~30% testing in the front end 7. Accessing Class Resources 1 New students can access class recordings and learning roadmaps through the school community. Multiple teams (Team Delta for beginners, Team Gamma for intermediate) offer structured progression.