---
schema_version: "1"
id: 7f183a2554b75400c3edf8c2698531661c68ee275dad7dd11ad6d74ef1c24b97
title: EinsteinAISettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_einsteinaisettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_einsteinaisettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 42f6ed901dea1a2a7bfbd9b935ae53618e5eb546b97524d654ecb743743e6f23
description: Represents Einstein AI settings, including AI feedback integration with Data 360 and PII masking for AI trust features.
---
# EinsteinAISettings

Represents Einstein AI settings, including AI feedback integration with Data 360 and PII masking for AI trust features.

## Parent Type and Manifest Access

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 the settings metadata types for the org 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 more details.

## File Suffix and Directory Location

EinsteinAISettings values are stored in the EinsteinAISettings.settings file in the settings folder. The .settings files are different from other named components, because there is only one settings file for each settings component.

## Version

EinsteinAISettings is available in API version 60.0 and later. Individual fields may have specific minimum API version requirements as noted in the field descriptions.

## Special Access Rules

There are no additional access requirements that are specific to this type.

## Fields

| Field Name | Description |
| --- | --- |
| enableAIFeedbackWithDC | 
Field Type

boolean

Description

Indicates whether AI feedback integration with Data 360 is enabled (true) or not (false). Available in API version 60.0 and later.



 |
| enableTrustPIIMasking | 

Field Type

boolean

Description

Indicates whether PII (Personally Identifiable Information) masking for AI trust features is enabled (true) or not (false). Available in API version 60.0 and later.



 |

## Declarative Metadata Sample Definition

The following is an example of an EinsteinAISettings component.

<?xml version="1.0" encoding="UTF-8"?>
<EinsteinAISettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <enableAIFeedbackWithDC\>true</enableAIFeedbackWithDC\>
    <enableTrustPIIMasking\>true</enableTrustPIIMasking\>
</EinsteinAISettings\>

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

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types\>
        <members\>EinsteinAI</members\>
        <name\>Settings</name\>
    </types\>
    <version\>64.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.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 information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/file_based_zip_file.htm "The deploy() and retrieve() calls are used to deploy and retrieve a .zip file. Within the .zip file is a project manifest (package.xml) that lists what to retrieve or deploy, and one or more XML components that are organized into folders.").