---
schema_version: "1"
id: 14d594f17e5cb44f8305b39a349c9a07432e4468b36125538f37db383a889355
title: UserManagementSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_usermanagementsettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_usermanagementsettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 5342b5c9280f8465d5981f99973c1f402b927f6d809100c894b0066a8ce836d4
description: Represents a selection of user management options that appear on the User Management Settings Setup page. This type extends the Metadata metadata type and inherits its fullName field.
---
# UserManagementSettings

Represents a selection of user management options that appear on the User Management Settings Setup page. This type extends the Metadata metadata type and inherits its fullName field.

In the package manifest, all organization settings metadata types are accessed using the Settings name. See [Settings](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_settings.htm "Represents the organization settings related to a feature. For example, your password policies, session settings and network access controls are all available in the SecuritySettings component type.") for details.

## File Suffix and Directory Location

UserMangementSettings are stored in the UserManagement.settings directory. The .settings files are different from other named components because there’s only one settings file for each settings component.

## Version

Manage org-wide settings for certain options. User Management Settings are available in API version 46.0 and later.

## Fields

<table class="featureTable sort_table" summary="">



          <thead class="thead sorted" align="left">
            <tr>
              <th class="featureTableHeader  " id="d945452e99">Field</th>

              <th class="featureTableHeader  " id="d945452e102">Field Type</th>

              <th class="featureTableHeader  " id="d945452e105">Description</th>

            </tr>

          </thead>

          <tbody class="tbody">
            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableConcealPersonalInfo</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates if personal information fields in user records are
                hidden from external users (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). When this field is set to <samp class="codeph nolang">true</samp>, 10 personal information
                fields are hidden. The default value is <samp class="codeph nolang">false</samp>. This field is unavailable for orgs created in
                Winter ’22 or later.<p class="p">Salesforce recommends that you use the
                  <span class="keyword parmname">enableEnhancedConcealPersonalInfo</span> field
                  instead of <span class="keyword parmname">enableConcealPersonalInfo</span>.
                  Before you set the
                  <span class="keyword parmname">enableEnhancedConcealPersonalInfo</span> field
                  to <samp class="codeph nolang">true</samp>, make sure that
                  <span class="keyword parmname">enableConcealPersonalInfo</span> is set to
                  <samp class="codeph nolang">false</samp>.
                </p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableContactlessExternalIdentityUsers</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">If <samp class="codeph nolang">true</samp> and your org has the
                External Identity license, you can create contactless users. Having
                users without contact information reduces the overhead of managing
                customers. Purchase the External Identity license to access the
                Customer 360 Identity product.<p class="p">The default is <samp class="codeph nolang">false</samp>. Available in API version
                  47.0 and later.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableEnhancedConcealPersonalInfo</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates if personal information fields in user records are
                hidden from external users (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). When this field is set to <samp class="codeph nolang">true</samp>, you can choose which fields
                are classified as personal information and hidden on the User
                Management Settings Setup page. The default value is <samp class="codeph nolang">false</samp>. This field is available in
                API version 53.0 and later.<p class="p">Before you set the
                  <span class="keyword parmname">enableEnhancedConcealPersonalInfo</span> field
                  to <samp class="codeph nolang">true</samp>, make sure that
                  <span class="keyword parmname">enableConcealPersonalInfo</span> is set to
                  <samp class="codeph nolang">false</samp>.
                </p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableEnhancedPermsetMgmt</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">If you enable <strong class="ph uicontrol">Enhanced Permission Set Component
                  Views</strong> (<samp class="codeph nolang">true</samp>),
                you can work with permission sets more easily. For example, when you
                have large numbers of Apex class assignments for permission sets,
                you can enable a paginated result set, standard filtering, and
                sorting.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableEnhancedProfileMgmt</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">If you enable <strong class="ph uicontrol">Enhanced Profile Lists Views</strong>
                (<samp class="codeph nolang">true</samp>), you can quickly
                view, customize, and edit list data.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableEnhcUiUserAccessPolicies</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates whether you create and manage user access policies
                through an improved user interface (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). The default value is <samp class="codeph nolang">false</samp>. If user access policies
                aren’t enabled, this field has no effect. If user access policies
                are enabled, this field is automatically set to <samp class="codeph nolang">true</samp>, but you can change it to
                <samp class="codeph nolang">false</samp>. Available in API
                version 60.0 and later.
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableNewProfileUI</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">If you enable <strong class="ph uicontrol">Enhanced Profile User
                  Interface</strong> (<samp class="codeph nolang">true</samp>), you can use the streamlined, enhanced profile user
                interface to browse, search, and modify settings. You can use only
                one user interface at a time.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableProfileFiltering</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">With profile filtering enabled (<samp class="codeph nolang">true</samp>), you can restrict who sees profile names to the
                users who require the access for their job roles. If profile
                filtering is disabled (<samp class="codeph nolang">false</samp>),
                users can see all profiles in a Salesforce org, regardless of which
                permissions they have. <p class="p">Profile names are also exposed when users
                  with permissions to perform the following tasks take these
                  actions:</p>
                <ul class="ul bulletList">
                  <li class="li">Create a tab or record type with a wizard step that includes
                    the assignment of tabs and record types to profiles.</li>

                  <li class="li">Configure a login flow where viewing profile lists is
                    required to make flow associations.</li>

                  <li class="li">Set up delegated admins where looking up profiles is needed
                    to identify assignable profiles.</li>

                  <li class="li">Administer an org as a delegated customer admin.</li>

                  <li class="li">Administer an org as a delegated admin to view and assign
                    profiles of the delegated group.</li>

                </ul>
                <p class="p">This field is available in API version 50.0 and
                  later.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableRestrictEmailDomains</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates whether the Email Domain Allowlist is visible (<samp class="codeph nolang">true</samp>) or hidden (<samp class="codeph nolang">false</samp>) in Setup. The default value
                is <samp class="codeph nolang">false</samp>.<p class="p">This field is
                  available in API version 53.0 and later.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableScrambleUserData</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">If you enable <strong class="ph uicontrol">Let Users Scramble Their User
                  Data</strong> (<samp class="codeph nolang">true</samp>),
                users can request that Salesforce remove all their personal data.
                Because Salesforce can’t delete information, it scrambles their
                data. Scrambling a user’s data is unrecoverable. So this org-wide
                setting serves as an extra precaution. If a user requests it, you
                scramble the data programmatically with the <samp class="codeph nolang">obfuscateUser</samp> Apex method. You can
                use the method, for example, in a custom Apex trigger, workflow, or
                the Developer Console.<p class="p">This field is available in API version 47.0
                  and later.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enableUserSelfDeactivate</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">If you enable <strong class="ph uicontrol">User Self Deactivate</strong>
                (<samp class="codeph nolang">true</samp>), users can
                deactivate their Experience Cloud site or Chatter accounts.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enhancedPermSetList</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates whether you manage permission sets with an updated user
                interface on the Permissions Setup page (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). The default value is <samp class="codeph nolang">false</samp>. Available in API version
                63.0 and later.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enhancedUserListView</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates whether you manage users with an updated user interface
                on the Users Setup page (<samp class="codeph nolang">true</samp>)
                or not (<samp class="codeph nolang">false</samp>). The default
                value is <samp class="codeph nolang">false</samp>. Available in
                API version 62.0 and later.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">enhancedUserRoleListView</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates whether you manage roles with an updated user interface
                on the Roles Setup page (<samp class="codeph nolang">true</samp>)
                or not (<samp class="codeph nolang">false</samp>). The default
                value is <samp class="codeph nolang">false</samp>. Available in
                API version 63.0 and later.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">groupSummaryUIEnhancement</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates whether you use an improved user interface to add or
                remove public group members through the group’s summary page <samp class="codeph nolang">true</samp> or not (<samp class="codeph nolang">false</samp>). If this field is set to
                <samp class="codeph nolang">true</samp>, you can still manage
                public group membership through the group’s detail page. The default
                value is <samp class="codeph nolang">true</samp>. Available in API
                version 62.0 and later.
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">permsetsInFieldCreation</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">If <samp class="codeph nolang">true</samp>, users can assign
                field-level security to permission sets instead of to profiles when
                creating a field on an object, setting field-level security on a
                field, or changing a field type on a field. The default is <samp class="codeph nolang">false</samp>. <p class="p">Available in API version
                  56.0 and later.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">psaExpirationUIEnabled</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates if admins can use an updated user interface that
                includes an assignment expiration for permission sets and permission
                set groups (<samp class="codeph nolang">true</samp>) or not
                (<samp class="codeph nolang">false</samp>). The default value
                is <samp class="codeph nolang">false</samp>. This field is
                available in API version 52.0 and later.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">restrictedProfileCloning</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">When enabled (<samp class="codeph nolang">true</samp>), only
                permissions accessible to your org are enabled when you clone
                profiles. When disabled (<samp class="codeph nolang">false</samp>), all permissions currently enabled in the source
                profile are also enabled for the cloned profile, even if your org
                can't currently access them.<p class="p">This field is available in API
                  version 50.0 and later.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">userAccessPoliciesEnabled</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates if user access policies are enabled (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). With user access policies,
                you can automate and migrate your users’ assignments to managed
                package licenses, permission sets, and other access mechanisms based
                on criteria that you set. The default value is <samp class="codeph nolang">false</samp>. This field is available in
                API version 58.0 and later.</td>

            </tr>

            <tr>
              <td class="entry" headers="d945452e99" data-title="Field"><span class="keyword parmname">userFieldHistoryTracking</span></td>

              <td class="entry" headers="d945452e102" data-title="Field Type">boolean</td>

              <td class="entry" headers="d945452e105" data-title="Description">Indicates if user field history tracking is enabled (true) or not
                (false). With user field history tracking, you can keep track of
                changes in user fields. The default value is <samp class="codeph nolang">false</samp>. This field is available in
                API version 64.0 and later.</td>

            </tr>

          </tbody>

        </table>

## Declarative Metadata Sample Definition

The following is an example of a UserManagementSettings component.

<?xml version="1.0" encoding="UTF-8"?>
<UserManagementSettings xmlns="http://soap.sforce.com/2006/04/metadata" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <enableConcealPersonalInfo\>false</enableConcealPersonalInfo\>
    <enableContactlessExternalIdentityUsers\>false</enableContactlessExternalIdentityUsers\>
    <enableEnhancedConcealPersonalInfo\>true</enableEnhancedConcealPersonalInfo\>
    <enableEnhancedPermsetMgmt\>false</enableEnhancedPermsetMgmt\>
    <enableEnhancedProfileMgmt\>true</enableEnhancedProfileMgmt\>
    <enableNewProfileUI\>false</enableNewProfileUI\>
    <enableProfileFiltering\>false</enableProfileFiltering\>
    <enableRestrictEmailDomains\>true</enableRestrictEmailDomains\>
    <enableScrambleUserData\>false</enableScrambleUserData\>
    <enableUserSelfDeactivate\>false</enableUserSelfDeactivate\>
    <enhancedPermSetList\>true</enhancedPermSetList\>
    <enhancedUserListView\>true</enhancedUserListView\>
    <enhancedUserRoleListView\>true</enhancedUserRoleListView\>
    <groupSummaryUIEnhancement\>true</groupSummaryUIEnhancement\>
    <restrictedProfileCloning\>true</restrictedProfileCloning\>
    <userAccessPoliciesEnabled\>true</userAccessPoliciesEnabled\>
</UserManagementSettings\>

The following is an example package.xml manifest that references the previous definition.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types\>
        <members\>UserManagement</members\>
        <name\>Settings</name\>
    </types\>
    <version\>53.0</version\>
</Package\>

## Wildcard Support in the Manifest File

The wildcard character \* (asterisk) in the package.xml manifest file doesn’t apply to metadata types for feature settings. The wildcard applies only when retrieving all settings, not for an individual setting. For details, see [Settings](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/meta_settings.htm). For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).