Omnistudio permission sets for health builders and end users
Key Takeaway
Builders get "Omnistudio Admin", end users get "Omnistudio User", and Agentforce Health features add their own permission sets alongside these.
Omnistudio is the no-code toolset Agentforce Health uses for guided interactions. Its components are Omniscripts, Flexcards, Integration Procedures, and Omnistudio Data Mappers. Two permission sets control who can build these components and who can only run them, so a customer design tells you which person needs which set.
The Omnistudio PSL and its two permission sets
Omnistudio access starts with the Omnistudio permission set license (PSL), renamed from Omnistudio Admin. The Omnistudio PSL now includes two permission sets: Omnistudio Admin and Omnistudio User.
A user gets no base-level access to Omnistudio objects until you assign one of these permission sets. So set them up and assign them before you use Omnistudio in Agentforce Health.
Omnistudio Admin is for builders, the admins and designers who create and manage Omnistudio content. Omnistudio User is for end users, also called consumers. End users can run components but cannot create or edit them. Omnistudio Admin also includes the permissions granted by Omnistudio User, so a builder does not need both sets.
| Omnistudio Admin | Omnistudio User | |
|---|---|---|
| Flexcards (Omni UI Card) | Create, Read, Update, Delete | Read |
| Omniscripts and Integration Procedures (both Omni Process) | Create, Read, Update, Delete | Read |
| Omnistudio Data Mappers (Omni Data Transformation) | Create, Read, Update, Delete | Read |
OmniGlobalAutoNumber | Create, Read, Update, Delete | Read, Update |
OmniInteractionAccessConfiguration | Read, through Omnistudio User | Read |
| Omniscript Saved Session | Full access, through Omnistudio User | Full access |