---
schema_version: "1"
id: 07ef33a4f57ac05835e1eb1bffa86cb3cce8efe5ae868ea116700bd2efe18c0f
title: Configuring Community Profiles for Omniscript (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_configuring_community_profiles_for_omniscript.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_configuring_community_profiles_for_omniscript.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 402e2e088c904c81f4d33dec1debf1e8a47147c6c35219916a62ea5be9f29212
description: For the managed package runtime, to allow deployment of an Omniscript from an Experience page, configure the following sharing settings and profile access.
products:
  - Omnistudio
release: "264"
---
# 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.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_important.png)

Important

Beginning with the Winter '20 Salesforce release, [Guest Users](https://help.salesforce.com/articleView?id=networks_public_access.htm&language=en_US), 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](https://www.learncommunitycloud.com/s/news/guest-user-record-access-development-best-practices-20Y1U000000UkITUA0).

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](https://help.salesforce.com/articleView?id=platform.networks_public_access.htm&type=5&language=en_US).

1. To configure sharing settings:
    1. From Setup, click **Security Controls** or **Security** and then click **Sharing Settings**.
    2. 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.
    3. To change the Default Internal Access or External Default Access for Vlocity Omniscript, click the **Edit** button next to Organization-Wide Defaults.
    4. For Vlocity Omniscript, set the Default Internal Access and External Default Access to **Public Read Only**.
    5. 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**.
    6. Click **Save**.
2. The prerequisite for these steps is that communities must exist in your org. For more information, see [Setting Up a Community](https://help.salesforce.com/articleView?id=networks_setup_maintain_communities.htm&type=5&language=en_US) in the Salesforce Help. To configure community user visibility:
    1. From Setup, click **Customize** or **Feature Settings**, then click **Communities**, then click **All Communities**.
    2. For the community to which you are granting access, click **Workspaces**, click **Administration**, then click **Members**.
    3. Make sure that all profiles that should access the community are in the **Selected Profiles** section, then click **Save**.
3. To ensure that you are using the Original Profile Interface:
    1. From Setup, type User in the Quick Find box and click **User Management Settings**.
    2. Set the Enhanced Profile User Interface option to **Disabled**.
4. To set field-level security:
    1. From Setup, click **Manage Users** or **Users**, then click **Profiles**.
    2. 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.
    3. Scroll down to the Field Level Security section and click **View** next to Application.
    4. Click **Edit** and click **Read Access** next to every field.
    5. Click **Save**.
    6. 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)](https://help.salesforce.com/s/articleView?id=xcloud.os_setting_object_permissions_and_enabling_apisvisualforce_pagesand_apex_access.htm&release=264.0.0&type=5)**  
    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)](https://help.salesforce.com/s/articleView?id=xcloud.os_applying_the_visualforce_page_for_omniscript_in_a_community.htm&release=264.0.0&type=5)**  
    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)](https://help.salesforce.com/s/articleView?id=xcloud.os_creating_a_community_user_from_an_application.htm&release=264.0.0&type=5)**  
    For the managed package runtime, the housing community provides clients with a self-service portal to interact with the agency and property management.