SocialProfileSettings

Represents org preferences for social media features such as enabling Twitter and Facebook.Represents org preferences for social media features such as enabling Twitter and Facebook.

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

Parent Type 

This type extends Metadata and inherits its fields.

File Suffix and Directory Location 

SocialProfileSettings values are stored in a single file named SocialProfile.settings in the settings directory of the corresponding package directory. The .settings files are different from other named components because there’s only one settings file for each settings component.

Version 

SocialProfileSettings is available in API versions 47.0 through 58.0.

Fields 

enableSocialProfiles 

• Type: boolean
• Required: No
• Description: Indicates whether users can access social media profiles in social CRM (true) or not (false).

isFacebookSocialProfilesDisabled 

• Type: boolean
• Required: No
• Description: Prevents users from accessing Facebook in social CRM (true) or not (false). enableSocialProfiles must be true to enable Facebook social profiles.

isLinkedInSocialProfilesDisabled 

• Type: boolean
• Required: No
• Description: Prevents users from accessing LinkedIn in social CRM (true) or not (false). enableSocialProfiles must be true to enable LinkedIn social profiles.

isTwitterSocialProfilesDisabled 

• Type: boolean

• Required: No

• Description: Prevents users from accessing Twitter in social CRM (true) or not (false). enableSocialProfiles must be true to enable Twitter social profiles.

  This setting is permanently set to True because Twitter access was removed in API version 59.0.

isYouTubeSocialProfilesDisabled 

• Type: boolean

• Required: No

• Description: Prevents users from accessing YouTube in social CRM (true) or not (false). enableSocialProfiles must be true to enable YouTube social profiles.

  This setting is permanently set to True because YouTube access was removed in API version 60.0.

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.