---
schema_version: "1"
id: 428abdcd8b14ed6fbe0610a31972e0af0083e2d3ae52b831d3e211d8bfff241a
title: Scanning Data 360 with Data Detect
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/data_detect_use_data_cloud.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.data_detect_use_data_cloud.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 403c79f96be8f2aa215b4cf2a65beff246633bdb25798eb009cd85d09bb36e87
description: Use Data Detect to scan Data 360 for sensitive data. Data 360 eliminates data silos, creating a single platform to access all of your organization data. Use Data Detect to scan and detect sensitive data in large batches within Data 360 to facilitate the correct handling of sensitive data. Selecting a DLO automatically targets all of its text fields. A single scan policy execution supports up to 100 DLOs.
products:
  - Salesforce Platform
  - Cross Cloud
release: "264"
---
# Scanning Data 360 with Data Detect

Use Data Detect to scan Data 360 for sensitive data. Data 360 eliminates data silos, creating a single platform to access all of your organization data. Use Data Detect to scan and detect sensitive data in large batches within Data 360 to facilitate the correct handling of sensitive data. Selecting a DLO automatically targets all of its text fields. A single scan policy execution supports up to 100 DLOs.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and
              <strong>Developer</strong>editions.
            </p>
            <p style="margin-bottom:0;">Requires the Salesforce Shield add-on subscription or the Data
              Detect add-on license and Data 360 licenses (Data Cloud Provisioning, Data Spaces , Storage
              Beyond Allocation).</p>
          </td>

        </tr>
      </tbody>
    </table>

## DLO Access

When selecting a DLO in Data Detect, it perfectly mirrors your data space configurations. You can only view and select DLOs in data spaces you have explicit permission to access. A single scan policy can span across multiple assigned data spaces.

Any users with permission to view Data Detect results see the aggregate metrics for all DLOs included in a scan.

## Differences When Scanning Data 360 with Data Detect

- You need a data stream to use Data Detect with Data 360. For complete information on setting up data streams, see [Data Sources in Data 360](https://help.salesforce.com/s/articleView?id=xcloud.c360_a_connectors.htm&language=en_US&type=5) and [Data Streams in Data 360](https://help.salesforce.com/s/articleView?id=xcloud.c360_a_data_streams.htm&language=en_US&type=5)
- Creating and running a scan policy is the same for Data 360 and a standard Salesforce Org. Objects in Data 360 are referred to as Data Lake Objects (DLOs) instead of standard objects.
- Data 360 scan policies can't scan for keywords.
- Data Detect doesn't support external DLOs and unstructured DLOs.
- Data Cloud ingests data continuously (with approximately 3-minute latency). Scans on live, actively updating DLOs can yield inconsistent results.
- Data 360 enforces a maximum limit of 31,072 characters per field value. Values exceeding this limit are truncated at the platform level before reaching the scan engine. The truncation can lead to incomplete scanning coverage for exceptionally long text fields.

![Warning](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_warning.png)

Warning Due to its underlying architecture, Data Detect can't differentiate between a physically deleted Data Lake Objects (DLOs) and structurally inaccessible due to profile permission changes.

If a DLO included in an active policy is deleted or becomes inaccessible, the policy is permanently deadlocked.

A deadlocked policy can't be viewed, run, edited, or cloned. All historical job session results associated with that policy are inaccessible.

To recover from a policy deadlock, create an entirely new policy from scratch or contact support for help with removing the deleted DLO from the policy.