Section 2 · Prompt Engineering · 20% of exam
2.2 Prompt Template Access Controls
Exam objective
Identify the permissions and Salesforce access considerations that govern who can create, manage, and execute prompt templates.
Prompt template access has two parts: access to manage the template and access to run it. Salesforce's exam guide calls out access controls because a working prompt is only useful when the right administrators can configure it and the intended users can execute it with appropriate data access. Do not assume that seeing a prompt in Prompt Builder means every user can run it, or that granting template access automatically grants access to the records and fields the prompt references.
Separate management from execution
Template managers create, edit, test, activate, and manage prompt templates. Salesforce identifies the Prompt Template Manager permission set for administrators who create and manage templates. The required permissions include Manage Prompt Templates and Execute Prompt Templates, or the applicable Customize Application permission described in Salesforce Help. A least-privilege setup grants management capability only to users responsible for authoring and maintaining templates.
Users who run templates need execution access. Salesforce documents the Prompt Template User permission set for accessing and running templates outside Prompt Builder. The exact permission needed can depend on how a template is invoked, for example through a Salesforce feature, an invocable action, or an integration. Confirm the calling context and assign only the required permissions. Where a custom permission set is used, check the object and feature access required by the template type and invocation method.
Respect data access at run time
A prompt can use merge fields and other resources. The user or automation context that supplies those resources matters. Salesforce data access can include object permissions, field-level security, sharing, and the execution context of a Flow or Apex action. If a user cannot access a record or field, do not solve the problem by broadly exposing it just so the prompt can produce a richer response. Review the data source, permission model, and output destination together.
For example, a case summary template might reference a sensitive field. The administrator must confirm that the intended service users are allowed to access that field and that the resulting text is appropriate for its destination. A template that writes output to a field also needs access to the target object and field. Access to execute the prompt is not a substitute for access to the data it reads or updates.
Test with representative users
Test with the permissions of the users who will actually run the template, not only with an administrator account. Check whether the template is visible, whether referenced resources resolve, whether output can be saved, and whether the response exposes only permitted information. If a template is invoked by Flow, inspect the Flow's inputs and run context. If invoked by Apex or an API, review that execution path and the parameters provided.
When a prompt works for an administrator but fails for another user, investigate both template execution permission and access to the referenced object, field, record, or invocation action.
Extra concept: Permission assignment and authorization are related but distinct. The template permission controls a capability; Salesforce's record and field security still governs the underlying CRM data. Official reference: Salesforce Help, Prompt Builder permissions - https://help.salesforce.com/s/articleView?id=ai.prompt_builder_about.htm&language=en_US&type=5
Key takeaways
- Separate authoring and management permissions from end-user execution access.
- Apply least privilege to template managers and users.
- Test prompt execution under realistic user access and invocation contexts.
