9.3 Agent Builder, Prompt Builder, and Grounding Concepts

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

9.3 Agent Builder, Prompt Builder, and Grounding Concepts

Key Takeaways Explain This Topic AI

Agentforce Builder is where admins and authorized builders create, customize, preview, and manage agents, while Prompt Builder helps create reusable prompt templates for generative AI experiences.

Instructions, subagents or topics, actions, variables, and grounding determine what an agent knows, how it reasons, and what it can do.

Grounding connects the agent to trusted Salesforce data, knowledge, files, or data libraries so responses are based on approved context rather than generic model output.

A Platform Administrator should understand configuration concepts, testing obligations, and handoff points to developers for Apex, complex integrations, or custom actions.

Last updated: May 2026

Builder concepts administrators should know

Agentforce Builder is the workspace for creating and customizing agents. Current Salesforce guidance also describes Agentforce Studio as a central app for building, testing, and monitoring agents, with access from the App Launcher when the org and user have the required feature access. Some older or transition documentation may still use the term topics where newer material uses subagents. For admin study, focus on the concept: a defined area of work that gives the agent instructions and allowed actions.

An agent configuration usually includes agent-level instructions, conversation behavior, subagents or topics, actions, variables, grounding sources, preview testing, and deployment settings. The admin should understand each part without needing to write Apex. Agent-level instructions define the agent identity, tone, boundaries, and refusal rules. Subagents or topics help route the user request to the right skill area. Actions let the agent do work, such as retrieve data, call a flow, create a record, or hand off a conversation.

Concept Admin meaning Study warning

Agent instructions Global behavior and boundaries Vague instructions produce inconsistent behavior.

Subagent or topic A focused work area for requests Do not create one giant area for unrelated tasks.

Action A capability the agent can perform Review permissions, validation, and rollback impact.

Variable Data passed into or used by prompts and actions Treat sensitive values like any other data exposure.

Grounding Trusted context supplied to the agent Bad or outdated sources produce bad answers.

Preview testing Builder-side testing before activation Admin-user testing is not enough for security.

Prompt Builder is related but not identical. Prompt Builder helps create prompt templates that can use Salesforce record fields, related data, and instructions to generate content in a repeatable way. For example, a sales team might use a prompt template to draft a follow-up email from opportunity details, recent activities, and approved messaging. An agent may use prompts as part of a broader conversational experience, but the admin should still separate template design from agent orchestration.

Grounding is the admin's bridge between generative output and trusted business context. A generic model can produce fluent text, but a business agent needs approved facts. Grounding can connect the agent to CRM records, knowledge articles, unstructured documents, or data libraries depending on the feature set. The admin should ask who owns each source, whether it is current, whether it is approved for the audience, and whether permission rules are enforced at runtime.

A strong grounding strategy is selective. Do not connect every document because more data feels safer. Too much uncurated content can make answers less reliable and harder to govern. Start with published knowledge, clear policy documents, or records with strong data quality. Remove duplicates, stale drafts, obsolete pricing, old procedure files, and confidential notes that do not belong in the agent's context.

Builder workflow for an admin-led pilot:

Confirm feature enablement, licensing, app visibility, and builder permissions.

Create or choose the right agent type or template for the use case.

Write agent-level instructions that define scope, tone, refusal behavior, and escalation.

Add subagents or topics for each focused business area.

Add grounded data sources and verify source ownership, publication status, and access rules.

Add actions only after reviewing validation rules, flow context, user permissions, and side effects.

Preview with happy paths, incomplete requests, restricted data requests, and unsupported tasks.

Save versions and document what changed before deployment.

Developer handoff is part of admin judgment. Flow actions may be admin-configurable when the process already exists and is safe to expose. Apex actions, external service calls, complex API integrations, custom data retrieval, and advanced error handling may require a developer or architect. The admin is still responsible for asking the right questions: what user context is used, what data leaves Salesforce, how errors are surfaced, and how the action is tested.

Prompt design has governance rules too. A good prompt template includes role, goal, data inputs, output format, and constraints. It should tell the AI what to do when information is missing, not encourage guessing. If the template drafts customer-facing content, the admin should include review steps, approved language, and brand or compliance constraints. For sensitive messages, AI can draft, but a human may still need to send.

Study trap: do not treat grounding as the same thing as permission. Grounding selects context sources, while permissions decide who can access records, fields, and actions. Both must be correct. Also do not assume a prompt template is safe because it works for an admin. Test with the users and records the business actually intends to support.