---
schema_version: "1"
id: c9100e6685dbda0d5cdc30de87182f6a79570cde21f58b14bdd04dc629932cf8
title: CollectionsDashboardSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_collectionsdashboardsettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_collectionsdashboardsettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 2a41817271fadc0df41defd9fe16b08b072fd991803937265e0f6c249c2dbce7
description: Represents an org’s settings to add the Collections Dashboard application to an org.
---
# CollectionsDashboardSettings

Represents an org’s settings to add the Collections Dashboard application to an org.

## Parent Type and Manifest Access

This type extends the [Metadata](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/metadata.htm "The base class for all metadata types. You can’t edit this object. A component is an instance of a metadata type.") metadata type and inherits its fullName field.

In the package manifest, all the settings metadata types for the org are accessed using the “Settings” name. 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 more details.

## File Suffix and Directory Location

CollectionsDashboardSettings values are stored in the CollectionsDashboard.settings file in the settings folder. The .settings files are different from other named components, because there’s only one settings file for each settings component.

## Version

CollectionsDashboardSettings components are available in API version 56.0 and later.

## Fields

| Field Name | Description |
| --- | --- |
| enableCollectionsDashboard | 
Field Type

boolean

Description

Indicates whether to add the Collections Dashboard application to an org (true) or not (false). The default value is false.



 |

## Declarative Metadata Sample Definition

Thisexample shows a sample CollectionsDashboardSettings component.

<?xml version="1.0" encoding="UTF-8"?>
<CollectionsDashboardSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <enableCollectionsDashboard\>true</enableCollectionsDashboard\>
</CollectionsDashboardSettings\>

Theis example shows a sample 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\>CollectionsDashboard</members\>
        <name\>Settings</name\>
    </types\>
    <version\>68.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.").