Omnistudio Fundamentals18% of the exam
Omnistudio licenses, permission set licenses and permission sets
Which permission set license and permission set each Omnistudio audience needs on the standard runtime (builders, internal users, authenticated and guest Experience Cloud users), what Omnistudio Admin and Omnistudio User grant, how to build the custom site permission sets, and why Enhanced Runtime Performance needs an extra permission set.
Explain Omnistudio license requirements, Permission Set licenses and Permission Sets.
~8 min read · 6 practice questions ·
What the exam expects
- Pick the permission set license and permission set for each audience: builders, internal viewers, authenticated Experience Builder Aura site users and guests.
- State what Omnistudio Admin and Omnistudio User grant on each Omnistudio object.
- Build the custom Experience Cloud user and guest user permission sets, including the guest restriction on saved sessions.
- Explain what Enhanced Runtime Performance changes (user mode) and the extra no-license permission set standard users then need.
Key terms:
- Permission set license (PSL): entitlement that lets a user be assigned permission sets that depend on it; Omnistudio's is named Omnistudio.
- Omnistudio Admin: full CRUD on Omnistudio objects, for people who build.
- Omnistudio User: read access for people who run components, plus saved-session access.
- Omnistudio Runtime for Communities PSL: license for authenticated users on Experience Builder Aura sites.
- User mode: execution that respects the running user's access levels.
Key facts
One PSL
- Detail
- The Omnistudio Admin PSL was renamed Omnistudio and holds both permission sets
Builders
- Detail
- Omnistudio PSL + Omnistudio Admin (full CRUD)
Internal viewers
- Detail
- Omnistudio PSL + Omnistudio User
Authenticated Aura site users
- Detail
- Omnistudio Runtime for Communities PSL + custom set
Guests
- Detail
- Omnistudio PSL + custom guest set
Omnistudio User saved sessions
- Detail
- Table: Create, Read, Update, Delete on Omniscript Saved Session; prose: Create (pages differ)
Guest saved sessions
- Detail
- Create, Edit and Delete deselected
Enhanced Runtime Performance
- Detail
- Components run in user mode
Standard user set
- Detail
- Clone Omnistudio User; both System Permissions checkboxes checked (read-only sets may leave the create-new-instances one off)
Extra permission set
- Detail
- No license; Omni Interaction Access Configurations; not needed for admins
Sources for this section (6)
- One Primary OmniStudio PSLhelp.salesforce.com (opens in a new tab)
- Omnistudio Permission Setshelp.salesforce.com (opens in a new tab)
- Guest User Permission Sethelp.salesforce.com (opens in a new tab)
- Omnistudio Settingshelp.salesforce.com (opens in a new tab)
- Standard User Permission Sethelp.salesforce.com (opens in a new tab)
- Enhanced Runtime Performance Permission Sethelp.salesforce.com (opens in a new tab)
- Which guest-set step removes a right from the cloned Omnistudio User set, and on which object?
- Why do admin users not need the extra Enhanced Runtime Performance permission set?
- When Help's prose and table disagree on saved-session access for Omnistudio User, what do you say?
- In the standard-user procedure, what must you confirm on System Permissions, and what may a read-only set skip?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 46 lessons of the Omnistudio Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (6 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams