---
schema_version: "1"
id: d2d0e5ec543ae1583a330b73837a5c1b8a0bed68fd115950d78a3d6e59bdcf43
title: AccountSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_accountsettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_accountsettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 66c3746d7b0826c4305b95eab3558dae5b9243b642eac92909e2a4dfafbc0861
description: Represents an org’s account settings for account teams, account owner report, and the View Hierarchy link.
---
# AccountSettings

Represents an org’s account settings for account teams, account owner report, and the **View Hierarchy** link.

This type extends the [Metadata](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/metadata.htm "The base class for all metadata types. You can’t edit this object. A component is an instance of a metadata type.") 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

AccountSettings values are stored in the Account.settings file in the settings folder. The .settings files are different from other named components because there’s only one settings file for each settings component.

## Version

AccountSettings is available in API versions 29.0 and later.

## Fields

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



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

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

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

            </tr>

          </thead>

          <tbody class="tbody">
            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">enableAccountDiscovery</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">When <samp class="codeph nolang">true</samp>, sets up Einstein Account Management dashboards and installs the related CRM Analytics and Customer Insights apps. The dashboards give users access to account health analytics including metrics on open pipeline, risk, and engagement scores. <p class="p">Einstein Account Management is part of Revenue Intelligence, which is available for an additional cost.</p>
                <p class="p">Available in API version 57.0 and later.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">enableAccountHistoryTracking</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">Indicates whether history tracking is enabled for accounts (<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 history tracking is disabled, the History related list is removed from account page layouts. However, history data is still available for reporting up to the date and time when tracking was disabled. Available in API version 47.0 and later.</td>

            </tr>

            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">enableAccountInsightsInMobile</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">Deprecated in API version 59.0 and later because the feature is no longer available. Indicates whether users can see Einstein Account Insights on their mobile device (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). Insights appear in the Einstein Insights component, which is on account records and the Home page.<p class="p">To use this feature, users must have the Einstein Account Insights permission.</p>
                <p class="p">Available in API version 47.0 to 58.0.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">enableAccountOwnerReport</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">Indicates whether the Account Owner Report can (<samp class="codeph nolang">true</samp>) or can’t (<samp class="codeph nolang">false</samp>) be run by all users.</td>

            </tr>

            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">enableAccountTeams</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">Indicates whether account teams are enabled (<samp class="codeph java">true</samp>) or not (<samp class="codeph nolang">false</samp>).<p class="p">The Metadata API can’t be used to disable account teams.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">enableContactHistoryTracking</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">Indicates whether history tracking is enabled for contacts (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). Available in API version 46.0 and later.</td>

            </tr>

            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">enableRelateContactToMultipleAccounts</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">Indicates whether users can relate a contact to multiple accounts (<samp class="codeph nolang">true</samp>) or only one account (<samp class="codeph nolang">false</samp>). The default value is <samp class="codeph nolang">false</samp>. If this feature (Contacts to Multiple Accounts) is disabled, secondary contact–account relationships created while the feature was enabled are deleted. Available in API version 47.0 and later.<p class="p">Avoid using the Metadata API to enable this feature. Use the Account Settings page in Setup to enable Contacts to Multiple Accounts.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">enableReportsToOnPersonAccount</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">Indicates whether the <strong class="ph uicontrol">Reports To</strong> field on Person Account, which corresponds to the <span class="keyword parmname">PersonReportsToId</span> field on the Account object, is enabled. The field allows users to associate person accounts and contacts with other person accounts or contacts that they report to.<p class="p">Available in API version 62.0 and later.</p>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d73409e116" data-title="Field Name"><span class="keyword parmname">showViewHierarchyLink</span></td>

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

              <td class="entry" headers="d73409e122" data-title="Description">Indicates whether the default <strong class="ph uicontrol">View Hierarchy</strong> link on all business account detail pages is visible (<samp class="codeph nolang">true</samp>) or hidden (<samp class="codeph nolang">false</samp>).</td>

            </tr>

          </tbody>

        </table>

## Declarative Metadata Sample Definition

The following is an example of the Account.settings file:

<?xml version="1.0" encoding="UTF-8"?>
<AccountSettings xmlns="http://soap.sforce.com/2006/04/metadata">
	<enableAccountDiscovery\>true</enableAccountDiscovery\>
	<enableAccountHistoryTracking\>true</enableAccountHistoryTracking\>
	<enableAccountInsightsInMobile\>false</enableAccountInsightsInMobile\>
	<enableAccountOwnerReport\>true</enableAccountOwnerReport\>
	<enableAccountTeams\>true</enableAccountTeams\>
	<enableContactHistoryTracking\>true</enableContactHistoryTracking\>
	<enableRelateContactToMultipleAccounts\>true</enableRelateContactToMultipleAccounts\>
	<enableReportsToOnPersonAccount\>true</enableReportsToOnPersonAccount\>
	<showViewHierarchyLink\>true</showViewHierarchyLink\>
</AccountSettings\>

## Example Package Manifest

The following is an example package manifest used to deploy or retrieve the Account settings metadata:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
	<types\>
		<members\>Account</members\>
		<name\>Settings</name\>
	</types\>
	<version\>29.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).