A government agency recently migrated to Salesforce and is very excited to be on board, but their System Administrators have doubts about installing…

According to the official Salesforce OmniStudio documentation, several prerequisite tasks must be completed within the Salesforce org before initiating the package installation. These include enabling specific standard features that OmniStudio components depend on. The three critical org-level configurations are: enabling Orders, enabling Person Accounts to support business-to-consumer or government-to-citizen models, and setting the organization-wide email deliverability access level to "All email". Completing these steps ensures that the target org has the required object schema and settings to prevent installation failures and ensure the proper functioning of post-installation scripts and core package features.

B. Enable Assets: The official OmniStudio installation guide does not list enabling Assets as a mandatory prerequisite for installing the core package.

E. Confirm browser settings meet published minimum requirements: While using a supported browser is a documented requirement for operating OmniStudio tools, the other three options are specific org configurations grouped as "Required Features" essential for the server-side package installation to succeed.

1. Salesforce Help. (2023). Before You Install the OmniStudio Package.

Reference: Under the section "Enable Required Features," the documentation explicitly lists the following prerequisites:

"Enable Orders"

"Enable Person Accounts"

"Set Email Deliverability to All Email"

This source directly validates answers A, C, and D as mandatory org-level configurations. It also validates that enabling Assets (B) is not a listed prerequisite.

2. Salesforce Help. (2023). OmniStudio Documentation.

Reference: The "Install OmniStudio" section consistently points to the prerequisite tasks mentioned above. The browser requirements are listed separately from the org feature enablement, highlighting a distinction between client-side usage requirements and server-side installation prerequisites. This supports the exclusion of option E in favor of the three required org features.