Prompt Template Manager versus Prompt Template User
Key Takeaway
Give builders Prompt Template Manager, which has Manage Prompt Templates and Execute Prompt Templates. Give end users who only run templates Prompt Template User, which has only Execute Prompt Templates.
Two permission sets control access to prompt templates, and they keep building templates separate from using them. Prompt Template Manager is for the people who create and manage prompt templates in Prompt Builder. Prompt Template User is for end users who only need to run those templates in their daily work.
What each permission set contains
| Who it is for | Manage Prompt Templates | Execute Prompt Templates | |
|---|---|---|---|
| Prompt Template Manager | Users who create and manage prompt templates in Prompt Builder | Yes | Yes |
| Prompt Template User | End users who access and run prompt templates outside Prompt Builder, through generative AI features | No | Yes |
Execute Prompt Templates is in both permission sets, so users with either one can run templates. Manage Prompt Templates is the permission that sets them apart, and only Prompt Template Manager includes it.
Running a template outside Prompt Builder covers everyday use.
For example, imagine a sales rep working in the Lightning Experience email composer. The rep picks a custom sales email prompt template there. Now imagine a user on a Lightning record page who clicks a generative AI-enabled field. That field uses a field generation prompt template. Both users are running a prompt template outside Prompt Builder.