---
schema_version: "1"
id: a9925c71de16d2c1c3777bad37ac00351560c5bc4507aa4ea3d12c51467c57d1
title: Salesforce Catalog Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_catalog_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_catalog_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 301945e011be3261b6a668f3bedd63615205afa2f42d78429ea5bff949728b7c
description: Note these considerations when you work with the Salesforce Catalog.
products:
  - Data 360
release: "264"
---
# Salesforce Catalog Considerations

Note these considerations when you work with the Salesforce Catalog.

- Salesforce Catalog is a Data 360 feature that can run on separate infrastructure, with different security protections and physical hosting locations than Agentforce Vibes. Review the [Salesforce Trust and Compliance Documentation](https://www.salesforce.com/company/legal/trust-and-compliance-documentation/).
- When you turn on Salesforce Catalog, Data 360 ingests your structural and operational metadata and generative AI enriches it.
- After you turn on Salesforce Catalog in a Data 360 sandbox, it applies to all associated sandboxes.
- To turn off and deprovision Salesforce Catalog after it's provisioned, contact Salesforce Customer Support.
- Salesforce Catalog isn't available in Developer Edition orgs if namespaces are enabled because search indexes aren't supported when namespaces are turned on.
- Salesforce Catalog isn't available in scratch orgs. Scratch org environments don’t support Data 360
- Salesforce Catalog doesn't support incremental metadata sync in Data Cloud One configurations. The catalog runs only daily full refresh cycles in Data Cloud One configurations.