You are here:
Configuring Community Profiles for Omniscript (Managed Package)
For the managed package runtime, to allow deployment of an Omniscript from an Experience page, configure the following sharing settings and profile access.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Beginning with the Winter '20 Salesforce release, Guest Users, also called anonymous users, cannot access any records by default. Criteria-based Sharing Rules grant them read-only access. This affects all Salesforce orgs. For details, see Guest User Record Access Development Best Practices.
Vlocity allows guest users to create and update the records to which Sharing Rules grant access. No additional configuration is necessary for this expanded access. To grant guest user access, see Give Secure Access to Unauthenticated Users with the Guest User Profile.
-
To configure sharing settings:
- From Setup, click Security Controls or Security and then click Sharing Settings.
- If you are in Lightning Experience, from the Manage sharing settings for drop-down list, select Vlocity Omniscript. If you are in Salesforce Classic, skip this step.
- To change the Default Internal Access or External Default Access for Vlocity Omniscript, click the Edit button next to Organization-Wide Defaults.
- For Vlocity Omniscript, set the Default Internal Access and External Default Access to Public Read Only.
- If you are writing to the Application object, follow the same steps to set the Default Internal Access and Default External Access for Application objects to Public Read/Write.
- Click Save.
-
The prerequisite for these steps is that communities must exist in your org. For
more information, see Setting Up a Community in the Salesforce
Help. To configure community user visibility:
- From Setup, click Customize or Feature Settings, then click Communities, then click All Communities.
- For the community to which you are granting access, click Workspaces, click Administration, then click Members.
- Make sure that all profiles that should access the community are in the Selected Profiles section, then click Save.
-
To ensure that you are using the Original Profile Interface:
- From Setup, type User in the Quick Find box and click User Management Settings.
- Set the Enhanced Profile User Interface option to Disabled.
-
To set field-level security:
- From Setup, click Manage Users or Users, then click Profiles.
-
Find the profile for the users who will be accessing the community and click
its name.
If you click Edit, you won't see the Field Level Security settings.
- Scroll down to the Field Level Security section and click View next to Application.
- Click Edit and click Read Access next to every field.
- Click Save.
- Repeat steps 3 through 5 for Vlocity Omniscript and Vlocity Omniscript Compiled Definition.
- Setting Object Permissions and Enabling APIs, Visualforce Pages, and Apex Access (Managed Package)
For the managed package runtime, Vlocity allows guest users to create and update the records to which Sharing Rules grant access. No additional configuration is necessary for this expanded access. - Apply the Visualforce Page for Omniscript in a Community (Managed Package)
For the managed package runtime, to configure the Visualforce Page for the Omniscript in a Community: - Create a Community User From an Application (Managed Package)
For the managed package runtime, the housing community provides clients with a self-service portal to interact with the agency and property management.
