---
schema_version: "1"
id: 4c54b169a9a2aa28491250c5282e9a0fcb86e27c8059c548e9daf5d3f51038ea
title: AgentforceForDevelopersSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_agentforcefordeveloperssettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_agentforcefordeveloperssettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 01c162b7400d447dcdd2119bcb0391f68f4a600fa57820d83750cfe25c0372d7
description: Represents Agentforce for Developers settings.
---
# AgentforceForDevelopersSettings

Represents Agentforce for Developers settings.

## 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 org 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 more details.

## File Suffix and Directory Location

AgentforceForDevelopersSettings values are stored in the AgentforceForDevelopers.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

AgentforceForDevelopersSettings are available in API versions 62.0 and later.

## Fields

| Field Name | Field Type | Description |
| --- | --- | --- |
| agentforceForDevelopersOptOut | boolean | Indicates whether Agentforce for Developers is enabled: true or false. If true, Agentforce for Developers isn't enabled in your org, which means that you've opted out of using it. If false, Agentforce for Developers is enabled. The default value is false. |

## Declarative Metadata Sample Definition

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

<?xml version="1.0" encoding="UTF-8"?>
        <AgentforceForDevelopersSettings xmlns="http://soap.sforce.com/2006/04/metadata">
        <agentforceForDevelopersOptOut\>false</agentforceForDevelopersOptOut\>
        </AgentforceForDevelopersSettings\>

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\>AgentforceForDevelopersSettings</members\>
         <name\>Settings</name\>
     </types\>
     <version\>62.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).