Prompt Engineering20% of the exam
Prompt template permissions and access controls
Who can build, activate and run prompt templates (Prompt Template Manager, Prompt Template User or Customize Application), and why the executing user's object access, sharing and field-level security decide which data a grounded prompt actually contains.
Identify access controls governing prompt templates.
~7 min read · 7 practice questions ·
What the exam expects
- Choose between the Prompt Template Manager and Prompt Template User permission sets from what a user must do: build and activate templates, or only run them.
- Name the alternate route to managing templates (Customize Application) and reject grants that are too broad or don't apply.
- Explain that grounding resolves in the executing user's context, so object permissions, record sharing and field-level security decide which merge fields, related lists and retrieved content reach the prompt.
- Troubleshoot "the summary is missing data for some users" by tracing the gap to the right access control.
- Key terms: Manage Prompt Templates (permission to create, edit and activate templates); Execute Prompt Templates (permission to run them); executing user (the person or automation user whose access the template runs with); secure data retrieval (grounding only with data that user can access); field-level security (FLS) (per-field read and edit access).
Key facts
Build and manage templates
- Detail
- Prompt Template Manager (Manage + Execute Prompt Templates) or Customize Application
Run templates
- Detail
- Prompt Template User (Execute Prompt Templates) or Customize Application
Manager assignment prerequisite
- Detail
- The user must have access to Setup
Who decides access
- Detail
- Admins manage who can use templates with permission sets
Generative field on a record page
- Detail
- Users need Prompt Template User to run it
Packaging pages that reference templates
- Detail
- Needs Manage Prompt Templates, or the template is left out of the package
Merge data at run time
- Detail
- Governed by the permissions of the executing user
Secure data retrieval
- Detail
- Preserves role-based controls and field-level security for CRM and Data 360 data
Related list grounding
- Detail
- No related list data if it's not on the user's layout or they lack Read
Retriever results
- Detail
- Row-level access checks apply to returned data and knowledge
Data 360 admin set name
- Detail
- Data Cloud Architect, formerly Data Cloud Admin
Sources for this section (9)
- Create a Prompt Templatehelp.salesforce.com (opens in a new tab)
- Enable Prompt Builderhelp.salesforce.com (opens in a new tab)
- Give Users Access to a Prompt Templatehelp.salesforce.com (opens in a new tab)
- Add a Field Generation Prompt Templatehelp.salesforce.com (opens in a new tab)
- Run-time Executionhelp.salesforce.com (opens in a new tab)
- Einstein Trust Layerhelp.salesforce.com (opens in a new tab)
- Related List Merge Fieldshelp.salesforce.com (opens in a new tab)
- Retrieve Datahelp.salesforce.com (opens in a new tab)
- Data 360 Standard Permission Setshelp.salesforce.com (opens in a new tab)
- Why does Prompt Template User suit intake staff better than Prompt Template Manager?
- When will related-list data be missing from a resolved prompt for one user?
- Which permission is the alternate route to building and managing prompt templates?
- Why can't adding a field as a template resource expose it to users without field access?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Agentforce Specialist pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Agentforce Specialist guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams