---
schema_version: "1"
id: a7b8714e27ff7db3e94874c6b7103f11ee2eeca4ba82555f82b45cec2834ee47
title: MeetingsSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_meetingssettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_meetingssettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 9e792723c2e0cae97b23e70db1a51aca9b6268a8c7fb70960678330b11ff76ec
description: Represents the settings to enable Salesforce Meetings and the integration with Zoom video conferencing.
---
# MeetingsSettings

Represents the settings to enable Salesforce Meetings and the integration with Zoom video conferencing.

## Version

MeetingsSettings components are available in API version 51.0 and later.

## Special Access Rules

The MeetingsSettings type isn’t available in scratch orgs.

## Fields

| Field Name | Description |
| --- | --- |
| enableSalesforceMeetings | 
Field Type

boolean

Description

Indicates whether the Salesforce Meetings feature is enabled (true) or not (false). When set to true, Salesforce admins can assign the Salesforce Meetings user permission to grant users access to the Meeting Digest and other Salesforce Meetings features. The default value is false.



 |
| enableSalesforceMeetingsSyncCheck | 

Field Type

boolean

Description

Indicates whether your company uses an activity sync solution (true) or hasn’t made that indication (false). Indicating your company uses an activity solution such as Einstein Activity Capture is required to enable Salesforce Meetings. The default value is false.



 |
| enableZoomVideoConference | 

Field Type

boolean

Description

Indicates whether users can connect their company Zoom accounts to Salesforce (true) or not (false). When set to true, Zoom can be added as a recording in Einstein Conversation Insights. The default value is false.



 |

## Declarative Metadata Sample Definition

The following is an example of a MeetingsSettings component.

<?xml version="1.0" encoding="UTF-8"?>
<MeetingsSettings xmlns="http://soap.sforce.com/2006/04/metadata">
        <enableSalesforceMeetings\>true</enableSalesforceMeetings\>
        <enableSalesforceMeetingsSyncCheck\>true</enableSalesforceMeetingsSyncCheck\>
        <enableZoomVideoConference\>false</enableZoomVideoConference\>
</MeetingsSettings\>

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\>MeetingsSettings</members\>
        <name\>Settings</name\>
    </types\>
    <version\>51.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.").