---
schema_version: "1"
id: dc757d79bd0a941bbf5c24710fa6ab50b58bdb6c17cb848f8ae640261a934397
title: SiteSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_sitesettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_sitesettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 47b584e440dba2e29bb481423660cafd9b7e58d73bfcc1bd07731da846a8a68c
description: Represents the settings for Experience Cloud sites and for Salesforce Sites.
---
# SiteSettings

Represents the settings for Experience Cloud sites and for [Salesforce Sites](https://help.salesforce.com/articleView?id=sites_overview.htm&type=5&language=en_US "HTML (New Window)").

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 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 "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 details.

## File Suffix and Directory Location

SiteSettings values are stored in a single file named Site.settings in the settings directory. The .settings files are different from other named components because there’s only one .settings file for each settings component.

## Version

SiteSettings components are available in API version 47.0 and later.

## Fields

<table class="featureTable sort_table" summary="">



          <thead class="thead sorted" align="left">
            <tr>
              <th class="featureTableHeader  " id="d875588e117">Field Name</th>

              <th class="featureTableHeader  " id="d875588e120">Field Type</th>

              <th class="featureTableHeader  " id="d875588e123">Description</th>

            </tr>

          </thead>

          <tbody class="tbody">
            <tr>
              <td class="entry" headers="d875588e117" data-title="Field Name"><span class="keyword parmname">enableEnhancedSitesAndContentPlatform</span></td>

              <td class="entry" headers="d875588e120" data-title="Field Type">boolean</td>

              <td class="entry" headers="d875588e123" data-title="Description">Indicates whether the enhanced sites and content platform for Experience Cloud is
                enabled for your org (<samp class="codeph nolang">true</samp>) or
                not (<samp class="codeph nolang">false</samp>). The default is
                <samp class="codeph nolang">true</samp>. When <samp class="codeph nolang">true</samp>, new LWR sites and enhanced
                CMS workspaces are hosted together on a redesigned platform that
                offers partial deployment, site content search, and easy content
                management. <span class="ph">Enhanced LWR sites are
                  represented by the <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_digitalexperiencebundle.htm" title="Represents a text-based code structure of your organization’s workspaces, organized by workspace type, and each workspace’s content items.">DigitalExperienceBundle</a> and <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_digitalexperienceconfig.htm" title="Represents details for your organization’s workspaces, such as the site label, site URL path prefix, and workspace type.">DigitalExperienceConfig</a>
                  types.</span> Available in API version 56.0 through 62.0. Removed
                in API version 63.0 and later.
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d875588e117" data-title="Field Name"><span class="keyword parmname">enableExpBuilderCopilot</span></td>

              <td class="entry" headers="d875588e120" data-title="Field Type">boolean</td>

              <td class="entry" headers="d875588e123" data-title="Description">Enables Agentforce (beta) in Experience Builder for enhanced LWR
                sites. The default value is <samp class="codeph nolang">false</samp>. Available in API 64.0 and later.<div class="p">
                  <div class="box message info">
                    <div class="inner">
                      <div class="bd">
                        <div class="media">
                          <img class="img mtm" src="https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/images/icon_note.png" alt="Note">
                          <div class="mediaBd">
                            <h4 class="mbs">Note</h4>
                            <p>Agentforce Experience Builder Agent is a pilot or beta
                              service that is subject to the Beta Services Terms at <a class="xref" href="https://www.salesforce.com/company/legal/" target="_blank">Agreements - Salesforce.com</a> or your written
                              Unified Pilot Agreement, and following terms in the <a class="xref" href="https://ptd.salesforce.com/?_ga=2.247987783.1372150065.1709219475-629000709.1639001992" target="_blank">Product
                                Terms Directory: Non-GA Agentforce</a>, the Non-GA
                              Open AI LLM Provider and the Non-GA Credit Consumption. Use
                              of this pilot or beta service consumes Einstein Requests and
                              is at the Customer’s sole discretion.</p>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>

                </div>
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d875588e117" data-title="Field Name"><span class="keyword parmname">enableExperienceFriendlyUrls</span></td>

              <td class="entry" headers="d875588e120" data-title="Field Type">boolean</td>

              <td class="entry" headers="d875588e123" data-title="Description">Indicates whether SEO-friendly URL snippets, or “slugs,” are
                enabled for your org (<samp class="codeph nolang">true</samp>) or
                not (<samp class="codeph nolang">false</samp>). The default is
                <samp class="codeph nolang">false</samp>. When <samp class="codeph nolang">true</samp>, available only in B2C
                Commerce LWR sites. Available only in API version 58.0. In API
                version 59.0 and later, use
                <span class="keyword parmname">expFriendlyUrlsAsDefault</span> in the <a class="xref" href="https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_network.htm" title="Represents an Experience Cloud site. Salesforce Experience Cloud lets you create branded spaces for your employees, customers, and partners. You can customize and create experiences, whether they’re communities, sites, or portals, to meet your business needs, then transition seamlessly between them. If you want to create zones that contain Chatter Answers and Ideas, use the Community (Zone) component.">Network</a> type.
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d875588e117" data-title="Field Name"><span class="keyword parmname">enableProxyLoginICHeader</span></td>

              <td class="entry" headers="d875588e120" data-title="Field Type">boolean</td>

              <td class="entry" headers="d875588e123" data-title="Description">Indicates whether security tokens for API logins from callouts
                (in API version 31.0 and earlier) are required (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). The default value is
                <samp class="codeph nolang">true</samp>.
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d875588e117" data-title="Field Name"><span class="keyword parmname">enableSitesRecordReassignOrgPref</span></td>

              <td class="entry" headers="d875588e120" data-title="Field Type">boolean</td>

              <td class="entry" headers="d875588e123" data-title="Description">Deprecated in API version 63.0 and later. When <samp class="codeph nolang">true</samp>, indicates when the org
                assigns records created by guest users of a site to a default owner
                in the org. When <samp class="codeph nolang">false</samp>, the
                guest user remains the owner of the record. The default value is
                <samp class="codeph nolang">false</samp>. Available in API
                version 48.0 through 63.0.
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d875588e117" data-title="Field Name"><span class="keyword parmname">enableTopicsInSites</span></td>

              <td class="entry" headers="d875588e120" data-title="Field Type">boolean</td>

              <td class="entry" headers="d875588e123" data-title="Description">Indicates whether guest and authenticated external users can view
                topics in Salesforce Sites and Salesforce portals (<samp class="codeph nolang">true</samp>) or not (<samp class="codeph nolang">false</samp>). The default value is
                <samp class="codeph nolang">false</samp>.
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d875588e117" data-title="Field Name"><span class="keyword parmname">enableVisualforceApiAccessAllowed</span></td>

              <td class="entry" headers="d875588e120" data-title="Field Type">boolean</td>

              <td class="entry" headers="d875588e123" data-title="Description">Deprecated in API version 52.0 and later. Allow users of
                Visualforce pages to override API access control restrictions and
                access APIs when the
                <span class="keyword parmname">enableAdminApprovedAppsOnly</span> in
                ConnectedAppSettings is enabled (<samp class="codeph nolang">true</samp>). The default value is <samp class="codeph nolang">false</samp>.
              </td>

            </tr>

            <tr>
              <td class="entry" headers="d875588e117" data-title="Field Name"><span class="keyword parmname">enableWebruntimeBYOTemplate</span></td>

              <td class="entry" headers="d875588e120" data-title="Field Type">boolean</td>

              <td class="entry" headers="d875588e123" data-title="Description">Indicates whether the Build Your Own (LWC) template is available
                in Experience Builder. The default value is <samp class="codeph nolang">false</samp>. Available in API version
                48.0 and later. Removed in API version 51.0.</td>

            </tr>

          </tbody>

        </table>

## Declarative Metadata Sample Definition

The following is an example of a SiteSettings component.

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

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\>Site</members\>
        <name\>Settings</name\>
    </types\>
    <version\>47.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.264.0.api_meta.meta/api_meta/meta_settings.htm). For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).