Type-specific permissions for prompt templates
Key Takeaway
Assign Prompt Template Manager to people who build and manage prompt templates in Prompt Builder. Assign Prompt Template User to end users who only run templates. Some template types need more: sales email templates also need the Einstein Sales Emails permission set.
Prompt templates use permission sets to separate the people who build templates from the people who run them. Some template types also need extra setup or an extra permission set before end users can use them. Two examples are sales email templates in Einstein Sales Emails and field generation templates on Lightning record pages.
Two roles: builders and end users
Prompt template access has two roles. Builders create and manage templates inside Prompt Builder. End users run templates through generative AI features outside Prompt Builder. Each role has its own permission set.
| Prompt Template Manager | Prompt Template User | |
|---|---|---|
| Role | Builders | End users |
| Assign it to | Users who need to create and manage prompt templates in Prompt Builder | End users who only need to access and run prompt templates |
| User permissions the role relies on | Manage Prompt Templates and Execute Prompt Templates | Execute Prompt Templates, because running a template relies on it |
For example, imagine an org where an admin designs prompt templates in Prompt Builder, and a team of users runs those templates through generative AI features. The admin gets Prompt Template Manager. The users only run templates, so they get Prompt Template User.
A user must have access to Setup before you can add them to the Prompt Template Manager permission set. After you assign Prompt Template Manager, refresh the page so Prompt Builder appears in Setup.
Einstein must be enabled in the org before either permission set is useful.