Running-user data access for prompt templates
Key Takeaway
Building and running prompt templates are separate jobs with separate standard permission sets: Prompt Template Manager for builders, and Prompt Template User for people who run templates. The running user needs permission to execute templates, not to manage them.
Prompt templates have two kinds of users: people who build them in Prompt Builder, and people who run them in their daily work. For example, a user might run a template to draft a field on a record page. Each group gets its own standard permission set. When a template runs, sensitive grounding data stays in Salesforce and isn't sent to the LLM.
Who builds templates and who runs them
Prompt template access is split into two jobs: creating and managing templates, and running them. Each job has its own standard permission set and needs its own permissions.
| Who does it | Standard permission set | Permissions needed | |
|---|---|---|---|
| Creating and managing templates | Users who create and manage templates in Prompt Builder | Prompt Template Manager | Manage Prompt Templates and Execute Prompt Templates |
| Running a template through generative AI features | End users who access and run templates outside Prompt Builder | Prompt Template User | Execute Prompt Templates |
The Customize Application permission meets either requirement.
A user must have access to Setup before they can be added to the Prompt Template Manager permission set. End users who only run templates should get Prompt Template User instead.
For example, generative AI-enabled fields on a Lightning record page use field generation prompt templates. Imagine a user who clicks one of these fields to draft its value. That user is running a template outside Prompt Builder, so they need the Prompt Template User permission set.