ContentSettings | Metadata API Developer Guide

In the package manifest, all organization settings metadata types are accessed using the Settings name. See Settings for more details.

File Suffix and Directory Location

ContentSettings values are stored in the contentsettings.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

ContentSettings components are available in API version 48.0 and later.

Fields

Field Name	Field Type	Description
enableChatterFileLink	boolean	When `true`, allows users to share files via links. When set to `false`, users can’t use file sharing. Default is `true`.
enableCMSC2CConnections	boolean	When `true`, allows org to enable Salesforce CMS Cloud to Cloud Connections.
enableContent	boolean	When `true`, allows org to enable Content.
enableContentAutoAssign	boolean	When `true`, allows org to auto assign Content feature licenses to users.
enableContentDistForPortalUsers	boolean	When `true`, allows portal users to create Content Deliveries for managed files in a library.
enableContentDistPwOptionsBit1	boolean	When `true`, allow using with `ContentDistPasswordOptionsBit2` to set up one of three possible delivery security options.
enableContentDistPwOptionsBit2	boolean	When `true`, allow using with `ContentDistPasswordOptionsBit1` to set up one of three possible delivery security options.
enableContentDistribution	boolean	When `true`, allows the Content Delivery user permission to be enabled for users. Content deliveries let users create links to share files externally, with optional security settings.
enableContentSupportMultiLanguage	boolean	When `true`, enables content to support multiple languages.
enableContentWorkspaceAccess	boolean	When `true`, content libraries are visible in the API and UI for users who have read access to libraries, even if they don't have access to the original Salesforce CRM Content app.
enableFileShareSetByRecord	boolean	When `true`, files shared to records will default to Set by Record.
enableFilesUsrShareNetRestricted	boolean	When `true`, files respect user sharing settings. Files shared with users with SharedUsers visibility are only accessible to users who are members of the Experience Cloud site the file was created in.
enableJPGPreviews	boolean	When `true`, attempts to use other SVG alternative formats such as JPG as preview images.
enableLibraryManagedFiles	boolean	When `true`, controls the ability to publish files created in Chatter with a Content Library (ContentWorkspace). The library can manage the file.
enableShowChatterFilesInContent	boolean	When `true`, allows users to search for Chatter files in content.
enableSiteGuestUserToUploadFiles	boolean	When `true`, site guest users can upload files.
enableUploadFilesOnAttachments	boolean	When `true`, shows the New File button on the Attachments related lists to upload files, rather than legacy Attachments.
skipContentAssetTriggers	boolean	When `true`, disables content trigger execution and custom validation on content assets.
skipContentAssetTriggersOnDeploy	boolean	When `true`, disables content trigger execution when deploying content assets.

Declarative Metadata Sample Definition

The following is an example of a Content.settings file.

1<ContentSettings xmlns="http://soap.sforce.com/2006/04/metadata">
2    <enableChatterFileLink>true</enableChatterFileLink>
3    <enableCMSC2CConnections>true</enableCMSC2CConnections>
4    <enableContent>true</enableContent>
5    <enableContentAutoAssign>true</enableContentAutoAssign>
6    <enableContentDistForPortalUsers>true</enableContentDistForPortalUsers>
7    <enableContentDistribution>true</enableContentDistribution>
8    <enableContentSupportMultiLanguage>false</enableContentSupportMultiLanguage>
9    <enableContentWorkspaceAccess>true</enableContentWorkspaceAccess>
10    <enableFileShareSetByRecord>true</enableFileShareSetByRecord>
11    <enableFilesUsrShareNetRestricted>true</enableFilesUsrShareNetRestricted>
12    <enableJPGPreviews>true</enableJPGPreviews>
13    <enableLibraryManagedFiles>true</enableLibraryManagedFiles>
14    <enableShowChatterFilesInContent>true</enableShowChatterFilesInContent>
15    <enableSiteGuestUserToUploadFiles>true</enableSiteGuestUserToUploadFiles>
16    <enableUploadFilesOnAttachments>true</enableUploadFilesOnAttachments>
17    <skipContentAssetTriggers>true</skipContentAssetTriggers>
18    <skipContentAssetTriggersOnDeploy>true</skipContentAssetTriggersOnDeploy>
19</ContentSettings>

The following is an example ContentSettings.xml manifest that references the ContentSettings definitions:

1<?xml version="1.0" encoding="UTF-8"?>
2<ContentSettings xmlns=
3    <types>
4        <members>Content</members>
5        <name>Settings</name>
6    </types>
7    <version>48.0</version>
8</ContentSettings>

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.