Study guide

7.3 Approval Processes, Email Alerts, and Notification Patterns

Salesforce Admin Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Administrator Orientation and Official Source Control

1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

2 Chapter 2: Configuration, Setup, User Management, and Org Controls

2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab

3 Chapter 3: Security, Access, Identity, and Sharing Model

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab

4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling

4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab

5 Chapter 5: Sales, Marketing, Service, and Support Applications

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab

6 Chapter 6: Data and Analytics Management

6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab

7 Chapter 7: Automation, Flow, Approval, and Operational Processes

7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab

8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange

8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab

9 Chapter 9: Agentforce for Platform Administrators

9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab

10 Chapter 10: Integrated Salesforce Admin Scenario Labs

10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy

11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy

11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review

7.3 Approval Processes, Email Alerts, and Notification Patterns

Key Takeaways Explain This Topic AI

Approval processes are best for formal review gates that need submitters, approvers, record locking, approval history, and final actions.

Email alerts and notifications should be designed around audience, urgency, record context, deliverability, and noise control.

Approval criteria, step criteria, delegated approvers, queues, and final actions must be tested with realistic users and records.

Notification automation should support operations without exposing sensitive data or creating duplicate messages.

Last updated: May 2026

Approval processes as controlled gates

An approval process is appropriate when a record must pass through a formal review before work continues. Common examples include discounts, contract exceptions, expense requests, knowledge article publication, high-risk account changes, or service credits. The value is not only that someone receives a message. The value is the submission event, approval steps, assigned approvers, record locking options, approval history, and final approval or rejection actions.

Approval process setup is found from Setup > Process Automation > Approval Processes . The admin defines the object, entry criteria, submitter settings, initial submission actions, approval steps, rejection behavior, recall behavior, and final actions. Each step can use criteria and assigned approvers. Approvers may be specific users, related users such as a manager, queues where supported by the process design, or delegated approver arrangements.

Entry criteria are the front door. If criteria are too broad, users submit records that do not need review. If criteria are too narrow, risky records bypass the gate. A discount process might require approval only when discount percent exceeds a threshold, amount is above a level, or a regulated product is included. The admin should confirm whether criteria use current field values, record type, owner role, region, or a custom approval status field.

Record locking must be understood. Locking can prevent users from editing a submitted record while approval is pending, which protects review integrity. However, it can also block legitimate operational edits, integrations, or data corrections. If a locked record needs updates, the admin must know who can unlock, whether final actions update fields, and how rejected records return to users for correction. Locking is a control, not a decoration.

Notifications and alerts design aid

Pattern Best use Risk to manage

Approval request email Tell an approver that action is required Approver lacks access, email is missed, or record details expose sensitive data.

Email alert from automation Send a templated message to users or contacts Duplicate emails, deliverability, outdated templates, and private field exposure.

Custom notification Alert users inside Salesforce or mobile Notification fatigue and unclear action context.

Task creation Put follow-up in a work queue or list Too many low-value tasks and poor ownership.

Chatter or feed post Collaborate around a record Sensitive details and overuse in high-volume automation.

Report subscription Periodic exception awareness Not real-time and limited by report visibility.

Email alerts are configured as reusable actions and can be invoked by approval processes, Flow, or other automation patterns depending on the org. Email templates should use fields that recipients are allowed to see and understand. For internal messages, include a record link, owner, status, and the action required. For external messages, validate branding, opt-out expectations, compliance language, and whether the message should be sent from Salesforce at all.

Custom notifications are often better than email when the recipient works in Salesforce all day or uses the mobile app. They can point users back to a record and avoid inbox clutter. They are not a replacement for a formal approval process when approval history and locking are required. They also need an audience strategy. Sending every notification to every manager will train users to ignore the system.

Notification design checklist:

Identify the action the recipient must take after receiving the message.

Confirm the recipient has record access and the right permission to complete the action.

Decide whether the message is immediate, scheduled, one-time, or repeatable.

Avoid including sensitive field values when a link to the secured record is safer.

Test email deliverability, template merge fields, mobile display, and queue behavior.

Monitor volume after release and remove duplicate alerts.

Approval scenarios and traps

Consider a high-discount opportunity approval. Sales reps submit the opportunity when discount percent is above 20 percent. The first step goes to the rep's manager. If the discount is above 35 percent or the amount is above 250,000, a second step goes to finance. Initial submission locks the record and sets Approval Status to Pending. Final approval sets Approval Status to Approved and notifies the deal desk. Final rejection sets Approval Status to Rejected and creates a task for the rep to revise terms.

This design has several test cases. A rep without a manager should not strand the request. A manager on vacation should have a delegated approver or operational coverage. A finance approver must be able to view the opportunity fields needed for review. A rejected opportunity must become editable enough for correction. A discount changed after approval may need resubmission. A data load should not accidentally submit hundreds of deals without business intent.

Approval and Flow can cooperate, but the boundary should be clean. Use approval processes for the formal gate and Flow for supporting actions that do not belong naturally in approval steps, such as creating a related implementation checklist after final approval. Avoid building a parallel approval engine in Flow unless the process requirement truly cannot be met by approval features. A custom flow-based approval is harder to audit and maintain unless the org has a deliberate reason.

Agentforce may help users prepare a submission summary or find policy guidance, but it should not silently approve records that require human accountability. If an AI-assisted experience suggests an approval path, the admin should verify permissions, grounding data, audit needs, and human review. The safer pattern is AI-assisted preparation plus deterministic approval routing.

Study traps include confusing notification with approval, assuming an email alert changes record access, and forgetting that record locking can block other automation. Another trap is placing all approvers in one step when the business requires sequential review. Read scenario wording carefully. If the requirement says approve, reject, lock, route to approver, or keep approval history, think approval process. If it only says inform a user or team, a notification pattern may be enough.