OrgSettings

Represents the settings for org-wide functionality that isn’t associated with any specific feature.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 for details.

File Suffix and Directory Location

A OrgSettings component file has the suffix .settings and is stored in the settings directory. The .settings files are different from other named components because there’s only one settings file for each settings component.

Version

OrgSettings components are available in API version 46.0 and later.

Before API version 51.0, the fields enableExtendedMailMerge and saveMailMergeDocsAsSalesforceDocs were found within OrgSettings components. In API version 51.0 and later, those fields are found within MailMergeSettings.

Fields

Field Name	Field Type	Descriptions

enableCustomerSuccessPortal	boolean	Indicates whether Customer Portal is enabled (`true`) or not (`false`).
enableManageSelfServiceUsers	boolean	Indicates whether mass management of self-service users is enabled through the Self-Service Portal (`true`) or not (`false`).
enableOrgFeedSentimentAnalysis	boolean	Indicates whether feed sentiment analysis is enabled for the org (`true`) or not (`false`).

Declarative Metadata Sample Definition

The following is an example of a OrgSettings component.

Example Package Manifest

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

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. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.

Metadata API Developer Guide