Omnistudio Fundamentals16% of the exam
Omnistudio licenses, permission set licenses and permission sets
Which Omnistudio permission set license and permission set each audience needs (builders, Lightning users, authenticated and guest site users), how to provision a cloned standard-user permission set, how to check that licenses are provisioned, and the access steps after install and at production cutover.
Explain Omnistudio license requirements, Permission Set Licenses and Permission Sets.
~7 min read · 8 practice questions ·
What the exam expects
- Name the Omnistudio permission set license and the two permission sets it includes, and explain the rename.
- Recommend a builder vs runtime-user access model that follows least privilege.
- Choose the license and permission set for authenticated and guest Experience Builder Aura site users, plus the guest sharing rule.
- Check that licenses are provisioned when an install fails on missing Omnistudio objects.
- List the access steps after a package install and before a production cutover.
- Key terms: permission set license (PSL) (entitles a user to permissions a permission set can then grant); Omnistudio PSL (formerly Omnistudio Admin PSL); Omnistudio Admin permission set (full CRUD for builders); Omnistudio User permission set (Read for consumers); Omnistudio Runtime for Communities PSL (authenticated Aura site users).
Key facts
Primary PSL
- Detail
- Omnistudio Admin PSL renamed Omnistudio; includes Omnistudio Admin and Omnistudio User
Why one PSL
- Detail
- The User PSL's standard permission set moved into it, for the standard objects model
Omnistudio Admin
- Detail
- Full CRUD on Omnistudio objects for admins and designers
Omnistudio User
- Detail
- Read on Omnistudio objects; saved sessions: Create (description) or CRUD (table) on the same page
Authenticated Aura site users
- Detail
- Omnistudio Runtime for Communities PSL plus a custom permission set
Guest Aura site users
- Detail
- Omnistudio PSL plus a custom guest permission set
Guest sharing
- Detail
- Omni Process rule, Guest user access based on criteria, Active equals true; children inherit
Standard user setup
- Detail
- Clone Omnistudio User; both System Permissions; access on four Omni objects
OmniUiCard or OmniProcess invalid at install
- Detail
- Licenses not provisioned; check Company Information and Object Manager
After package install
- Detail
- Configure Remote Site Settings and assign permission sets
Sources for this section (6)
- Omnistudio Permission Setshelp.salesforce.com (opens in a new tab)
- One Primary OmniStudio PSLhelp.salesforce.com (opens in a new tab)
- Guest User Sharing Rulehelp.salesforce.com (opens in a new tab)
- Standard User Permission Sethelp.salesforce.com (opens in a new tab)
- Troubleshooting Package Installation Errorshelp.salesforce.com (opens in a new tab)
- Install or Upgrade the Omnistudio Packagehelp.salesforce.com (opens in a new tab)
- Why don't standard-objects customers create their own Omnistudio User permission set any more?
- When does a site user need the Omnistudio Runtime for Communities PSL?
- How do you set up a read-only standard user from the shipped permission set?
- What must happen right after installing the Omnistudio managed package?
- Why assign the PSL and permission sets before a production cutover?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Omnistudio Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams