---
schema_version: "1"
id: 6ec9600219574b1b0e3a6d6e87468ea377cfedd4001eda0d67ef819b2f67a833
title: IndustriesSettings
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/service-cloud/salesforce-scheduler-dev-guide/guides/salesforce-scheduler/metadata-api/meta-scheduler-industriessettings.md
canonical_url: https://developer.salesforce.com/docs/service/salesforce-scheduler-dev-guide/guide/meta-scheduler-industriessettings.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: a7dd1a5af26b78164279cffe3a244b03adc03317e6f0cac9ae49aa9ebf36f0bb
products:
  - Salesforce Scheduler Developer Guide
  - Service Cloud Developer Content
---

# IndustriesSettings

Represents settings for Salesforce Scheduler.

This type extends the [Metadata](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/metadata.htm) metadata type and inherits its `fullName` field.

In the package manifest, all organization 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) for more details.

## File Suffix and Directory Location

IndustriesSettings are stored in a single file named `Industries.settings` in the `settings` directory.

## Version

Industries settings for Salesforce Scheduler are available in API version 47.0 and later.

## Fields

### appointmentDistributionOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether to schedule appointments for service resources based on appointment distribution (`true`) or not (`false`). Available in API version 52.0 and later.
-   **Default value**: `false`

### captureResourceUtilizationOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether to use a background process to calculate the usage of service resources from service appointments (`true`) or not (`false`). Available in API version 52.0 and later.
-   **Default value**: `false`

### enableAnyResourceTypeOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether to enable Salesforce Scheduler to consider service resource records with Agent resource type (`true`) or not (`false`). Before enabling this setting, create a service resource record as Main for each user, or update one of the service resource records as Main for each user. Available in API version 57.0 and later.
-   **Default value**: `false`

### enableAppFrmAnywhereOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether to use engagement channels for setting up shifts, work types, and booking a service appointment (`true`) or not (`false`). Available in API version 56.0 and later. See the [prerequisites](https://help.salesforce.com/s/articleView?id=platform.ls_prereqs_for_using_engagement_channels.htm&type=5) before you enable this setting.
-   **Default value**: `false`

### enableBlockResourceAvailabilityOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether Salesforce Scheduler service appointments are added to users' Salesforce calendars. For example, if set to `false`, users don’t see their service appointments on their calendars. The default is `false`. Available in API version 47.0 and later. This setting is used in Financial Services Cloud.

### enableCapacitySchedulingPref

-   **Field Type**: boolean
-   **Description**: Indicates whether users can use capacity-based scheduling (`true`) or not (`false`). Use capacity-based scheduling to control the number of appointments that can be scheduled for a given shift and type of work. Available in API version 62.0 and later. See the [prerequisite](https://help.salesforce.com/s/articleView?id=platform.ls_prereqs_capacity_based_scheduling.htm) before you enable this setting.

### enableCreateMultiAttendeeEventOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether users can group individual events, and view the list of all attendees under a single event `true` or not `false`. See the [prerequisites](https://help.salesforce.com/s/articleView?id=platform.ls_prereqs_multiple_attendee_event.htm&type=5) before you enable this setting. Available in API version 55.0 and later. This setting is used in Financial Services Cloud.
-   **Default value**: `false`

### enableDropInAppointmentsOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether users can manage drop-in participants (`true`) or not (`false`). Available in API version 58.0 and later. See the [prerequisite](https://help.salesforce.com/s/articleView?id=platform.ls_prereqs_drop_in_appointments.htm&type=5) before you enable this setting.
-   **Default value**: `false`

### enableDropInSkillMatchingOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether skill and skill level matching is enabled for service resources that are assigned to waitlists for a service territory (`true`) or not (`false`). Available in API version 58.0 and later.
-   **Default value**: `false`

### enableEventManagementOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether users can add Salesforce Scheduler service appointments to their Salesforce calendars. Available in API version 47.0 and later. This setting is used in Financial Services Cloud.
-   **Default value**: `false`

### enableEventWriteOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether to publish high-volume platform events when users create, update, or delete service appointments in Salesforce Scheduler (`true`) or not (`false`). If enabled, write these events to an external system to update it with Salesforce Scheduler service appointments. Available in API version 49.0 and later.
-   **Default value**: `false`

### enableMultipleTopicsForShiftsOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether the multiple topics for shifts feature is enabled (`true`) or disabled (`false`). Available in API version 56.0 and later. See the [prerequisite](https://help.salesforce.com/s/articleView?id=sf.ls_prereqs_multiple_topics_to_shifts.htm) before you enable this setting.
-   **Default value**: `false`

### enableMultiResourceOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether users can add multiple service resources to a service appointment. Available in API version 47.0 and later. This setting is used in Financial Services Cloud.
-   **Default value**: `false`

### enableOverbookingOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether users can add multiple service appointments to a single time slot for a service resource. If set to `false`, concurrent time slots are visible, but can't be modified. Available in API version 47.0 and later. This setting is used in Financial Services Cloud.
-   **Default value**: `false`

### enableShareSaWithArOrgPref

-   **Field Type**: boolean
-   **Description**: Indicates whether to share service appointments with assigned resources (`true`) or not (`false`). Available in API version 55.0 and later.
-   **Default value**: `false`

### enableTopicOrTemplate

-   **Field Type**: boolean
-   **Description**: Indicates whether to use Salesforce Scheduler to manage Health Cloud appointments (`true`) or not (`false`). You must enable the `enableTopicTimeSlot` field before enabling this setting. Available in API version 52.0 and later.
-   **Default value**: `false`

### enableTopicTimeSlot

-   **Field Type**: boolean
-   **Description**: Indicates whether to set operating hours for Service Territory Members for Work Type Groups (`true`) or not (`false`). Available in API version 52.0 and later.

    See the [prerequisites](https://help.salesforce.com/s/articleView?id=platform.ls_prereqs_operating_hours_for_resources_working_on_appointment_topics.htm&type=5) before you enable this setting. After you enable this setting, you can't disable it.

-   **Default value**: `false`

## Declarative Metadata Sample Definition

The following is an example of an Industries.Settings metadata file.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<IndustriesSettings xmlns="http://soap.sforce.com/2006/04/metadata">
   <appointmentDistributionOrgPref>true</appointmentDistributionOrgPref>
   <captureResourceUtilizationOrgPref>true</captureResourceUtilizationOrgPref>
   <enableBlockResourceAvailabilityOrgPref>true</enableBlockResourceAvailabilityOrgPref>
   <enableCreateMultiAttendeeEventOrgPref>true</enableCreateMultiAttendeeEventOrgPref>
   <enableDropInSkillMatchingOrgPref>true</enableDropInSkillMatchingOrgPref>
   <enableEventManagementOrgPref>true</enableEventManagementOrgPref>
   <enableAppFrmAnywhereOrgPref>true</enableAppFrmAnywhereOrgPref>
   <enableAnyResourceTypeOrgPref>true</enableAnyResourceTypeOrgPref>
   <enableDropInAppointmentsOrgPref>true</enableDropInAppointmentsOrgPref>
   <enableEventWriteOrgPref>true</enableEventWriteOrgPref>
   <enableMultipleTopicsForShiftsOrgPref>true</enableMultipleTopicsForShiftsOrgPref>
   <enableMultiResourceOrgPref>true</enableMultiResourceOrgPref>
   <enableOverbookingOrgPref>true</enableOverbookingOrgPref>
   <enableShareSaWithArOrgPref>true</enableShareSaWithArOrgPref>
   <enableTopicOrTemplate>true</enableTopicOrTemplate>
   <enableTopicTimeSlot>true</enableTopicTimeSlot>
</IndustriesSettings>
```

The following is an example `package.xml` that references the previous definition.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
   <types>
       <members>Industries</members>
       <name>Settings</name>
   </types>
   <version>47.0</version>
</Package>
```

