Study guide

4.2 Access Controls Governing Prompt Templates

Salesforce Certified Agentforce Specialist Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & How Agentforce Agents Work

1.1 Agentforce Specialist (AI-201) Exam Facts & Spring '26 Blueprint 1.2 How an Agent Works & the Building Blocks of Agent Script 1.3 Hybrid Reasoning: Agent Script in Canvas View and Script View

2 Chapter 2: Deterministic Control, Topics (Subagents) & Actions

2.1 Deterministic Behavior: Filters, Variables & Template Expressions 2.2 Standard and Custom Topics (Subagents) 2.3 Standard and Custom Agent Actions

3 Chapter 3: Agent Types, Security Context, Channels & Agent API

3.1 When to Use an Employee Agent or a Service Agent 3.2 Security Context: Who the Agent Runs As and How It Affects Actions 3.3 Connecting Agents to Channels: Digital Experiences, Email, Voice & Slack 3.4 When to Use the Agent API

4 Chapter 4: Prompt Builder Fundamentals

4.1 When to Use Prompt Builder 4.2 Access Controls Governing Prompt Templates 4.3 Prompt Template Types: Field Generation, Flex & More 4.4 Creating, Activating & Executing Prompt Templates

5 Chapter 5: Grounding, Prompt Best Practices, Trust Layer & Model Access

5.1 Choosing the Right Grounding Technique 5.2 Best Practices for Writing Effective Prompts 5.3 Einstein Trust Layer Security and Privacy Features 5.4 Managing and Preventing Access to Specific Models

6 Chapter 6: Data 360 Fundamentals for Agentforce

6.1 Agentforce Data Library: Types and Concepts 6.2 Chunking: Breaking Content Into Retrievable Units 6.3 Indexing and Search Types: Vector, Hybrid & Keyword 6.4 Retrievers: Individual, Ensemble & Filtered Retrieval

7 Chapter 7: Testing Agents with Testing Center

7.1 Testing an Agent with Testing Center 7.2 How Testing Center Evaluations Work

8 Chapter 8: Deploying Agents and Prompt Templates

8.1 Deploying an Agent from Sandbox to Production 8.2 Deploying Prompt Templates from Sandbox to Production

9 Chapter 9: Governance and Observability

9.1 Managing and Monitoring Agents 9.2 Agent Analytics and Agent Optimization

10 Chapter 10: Multi-Agent Orchestration, MCP & A2A

10.1 When a Multi-Agent Architecture Is Appropriate 10.2 Open Multi-Agent Protocols: MCP and A2A

4.2 Access Controls Governing Prompt Templates

Key Takeaways Explain This Topic AI

The Prompt Template Manager permission set (Manage Prompt Templates and Execute Prompt Templates) lets users create and manage templates in Prompt Builder.

The Prompt Template User permission set (Execute Prompt Templates) lets users access and run prompt templates outside Prompt Builder.

Secure data retrieval grounds prompts only with data the executing user can access, preserving field-level security and sharing.

Creating and managing retrievers needs Data Cloud permissions, and running prompts that use retrievers needs the Data Cloud User permission set.

Agentforce Service agent users get Prompt Template User through the AgentforceServiceAgentUserPsg permission set group.

Last updated: September 2026

4.2 Access Controls Governing Prompt Templates

Quick Answer: Two permission sets do most of the work. Prompt Template Manager (Manage Prompt Templates + Execute Prompt Templates) is for people who build and manage templates in Prompt Builder. Prompt Template User (Execute Prompt Templates) is for people, or agent users, who run templates in Salesforce features. Customize Application is an alternative for both. Beyond that, the executing user's data access controls what grounding data appears, and Data Cloud permission sets control retrievers.

The Two Core Permission Sets

Permission set Included permissions Who gets it What it allows

Prompt Template Manager Manage Prompt Templates, Execute Prompt Templates Admins and builders Create, edit, version, activate, and preview templates in Prompt Builder

Prompt Template User Execute Prompt Templates Business users, and agent users running template-based actions Access and run templates outside Prompt Builder (generative fields, sales emails, agent actions)

Customize Application can substitute for either. To be assigned Prompt Template Manager, a user must have access to Setup , because Prompt Builder lives there.

Enabling Prompt Builder

Set up Einstein generative AI (turn on Einstein in Einstein Setup).

For sales email templates, turn on Sales Emails in Einstein for Sales and assign the related permission set to reps.

Assign Prompt Template Manager to builders.

Assign Prompt Template User to end users who run templates.

Refresh so Prompt Builder appears in Setup.

Access for Specific Template Scenarios

Scenario Access requirement

A user needs to click the generate icon on a field generation field Prompt Template User . The admin must also assign the template to the field in Lightning App Builder (Dynamic Forms)

A custom permission set is used instead of the standard ones and field generation templates don't appear Grant object access to prompt templates plus the ExecutePromptTemplate and ManagePromptTemplate permissions

Reps use sales email templates Sales Emails turned on in Einstein for Sales, the related permission set assigned to reps, and access to run templates

A template uses an Einstein Search retriever Data Cloud permission set to create and manage retrievers; Data Cloud User to run prompts with Einstein search. Retriever data access follows Data Cloud permissions and the default data space

A builder wants the View this model link in Template Settings Data Cloud Admin permissions to open model configuration in AI Models

An agent action runs a template for a Service agent The agent user needs Prompt Template User , which it gets through the AgentforceServiceAgentUserPsg permission set group

An Employee agent runs a template action The logged-in user needs Prompt Template User

Packaging a Lightning page that references a template Manage Prompt Templates , or the template isn't included in the package

Creating a 2GP package version with templates The build user needs the Prompt Template Manager permission set ( EinsteinGPTPromptTemplateManager ) through packageMetadataAccess

Grounding Respects the Running User

The Einstein Trust Layer's secure data retrieval means a prompt is grounded only with data the executing user has access to :

Merge fields for records, related lists, flows, and Apex resolve using the permissions of the user executing the prompt .

Standard role-based controls and field-level security are preserved when grounding from CRM or Data 360.

Grounding is dynamic . It happens at run time and depends on who is running the template.

Two users running the same template on the same account can get different resolved prompts . If a field is hidden from one user by FLS, it never enters that user's prompt. That's a feature, not a bug.

The same principle applies to retrievers. Access checks on results ensure a user or agent can reach the underlying records, and records the caller can't access don't appear in results.

Where Access Mistakes Show Up

Symptom Likely cause Fix

Admin sees Prompt Builder, but a rep gets no generate icon on the field Rep lacks Prompt Template User , or the template isn't assigned to the field on the Dynamic Forms page Assign the permission set and configure the field in Lightning App Builder

A template action works in preview for the admin but fails for a Service agent The agent user lacks Prompt Template User, or access to the objects and fields the template reads Check the agent user's permission set group and object and field permissions

Retriever-grounded responses come back empty for service reps Reps lack Data Cloud User or access to the default data space, or Knowledge permissions Assign Data Cloud User, including the default data space, and Knowledge access

A new template version is ready, but users still get the old behavior The new version isn't activated Activate the new version (an access-adjacent control over which version users get)

A custom field just created isn't available as a resource Prompt Builder doesn't show new custom objects or fields immediately Log out and log back in

Least Privilege for Template Builders

Give Prompt Template Manager only to people who should change what the LLM is told. Template instructions shape customer-facing output.

Keep Prompt Template User broad enough for the teams that need generative features, and no broader.

Changes to templates aren't tracked in the Setup Audit Trail , so use version history, sandbox testing, and deployment controls for governance.

Exam Traps

Manager builds; User runs. Don't pick Prompt Template Manager for reps who only run templates.

Grounding follows the executing user , not the template author.

Retrievers need Data Cloud permissions in addition to the prompt template permission sets.

Service agent users already include Prompt Template User through the default permission set group, but they still need object and field access for grounding.