---
schema_version: "1"
id: 7a615ff6a906e259110192cadf93dfa206cd9d6208f67eccd4a468706f1e1c2b
title: Create a Community User From an Application (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_creating_a_community_user_from_an_application.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_creating_a_community_user_from_an_application.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: df3d6950496a2c099185f6b6627c8aa4beb845c3d84e4296e0e6fe50c4b5927f
description: For the managed package runtime, the housing community provides clients with a self-service portal to interact with the agency and property management.
products:
  - Omnistudio
release: "264"
---
# 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.

![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).

It’s possible to automate the creation of an external (Salesforce Community) user after a prospective tenant fills out the initial intake form, requesting assistance. To automate that user creation, follow these steps.

To create an external user when a form is submitted:

1. Add a **Remote Action** to the end of the **Omniscript** and configure the settings as follows:
    
    ```
    Remote Class = ExternalUserSelfRegistration
    Remote Method = selfReg
    ```
2. Create **elements** in the Omniscript for **Username** and **Password**. Alternatively, if an email address is already an element in the form, you can set the email address as the username. If no password element is added, a system-generated email is sent to the user with instructions for setting up their password for the portal. There are two optional remote options to add as Key/Value pairs:
    
    - **profileId**: To create a user with a different profile than the default one set up in the community, enter **profileId** as the key and the Id of the profile as the value.
    - **sendEmail**: To decide if a confirmation email is sent to new users, enter a boolean in the value field.
3. Create a Pre-Transform Omnistudio Data Mapper Interface to add to the remote action. The purpose of the Pre-Transform Data Mapper Interface is to map fields in the application (such as Name, Email, Password) to the required inputs for registration.

![Example](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_example.png)

Example Pre-Transform Data Mapper Interface

![Example pre-transform DataRaptor interface](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/omnistudio_for_managed_packages/images/omniscript_pretransform_dr_interface.gif)