Cloud Data Loss Prevention (Cloud DLP) is now a part of Sensitive Data Protection. The API name remains the same: Cloud Data Loss Prevention API (DLP API). For information about the services that make up Sensitive Data Protection, see Sensitive Data Protection overview.
Profile data in an entire organization except for select projects
You can turn on discovery for an entire organization, excluding certain
projects. This is useful, for example, if you want to use your
organization-level discovery
subscription for
most—but not all—projects.
Create a scan configuration at the organization level.
In the scan configuration, add a schedule and specify filters that match only
the projects that you don't want to profile.
In the Frequency tab, turn off Do profile this data.
Click Done.
Optional: You can add more schedules to specify how certain subsets of your
organization data should be profiled. Any data that isn't specified in a
schedule is profiled according to the Catch-all schedule.
Optional: If needed, edit the catch-all schedule.
Complete the rest of the scan configuration steps.
Profile select projects or data assets in an organization or folder
If you want to profile only a few projects or data assets across an organization
or folder, follow these steps:
Create a scan configuration at the organization or folder level.
In the scan configuration, add a schedule and specify filters that match only
the projects or assets that you want to profile.
Specify the frequency and conditions for profiling the data that you
selected.
Click Done.
Specify that all other data in the organization or folder shouldn't be
profiled:
Go to Catch-all schedule, which is the last schedule in the
Schedules list.
Turn off Profile the resources that don't match any custom schedule.
Complete the rest of the scan configuration steps.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Common discovery enablement scenarios\n\nThis page provides high-level instructions on how to set up your discovery scan\nconfiguration for common organization-level enablement scenarios.\n\nFor information about how to create or edit a scan configuration,\nsee [Manage scan configurations](/sensitive-data-protection/docs/manage-scan-configurations).\n\nProfile data in an entire organization except for select projects\n-----------------------------------------------------------------\n\nYou can turn on discovery for an entire organization, excluding certain\nprojects. This is useful, for example, if you want to use your\n[organization-level discovery\nsubscription](/sensitive-data-protection/pricing#discovery-subscription-mode-pricing) for\nmost---but not all---projects.\n| **Note:** An excluded project can still be profiled through a scan configuration with a different scope, like a project-level scan configuration.\n\n1. Create a scan configuration at the organization level.\n2. In the scan configuration, add a schedule and specify filters that match only the projects that you don't want to profile.\n3. In the **Frequency** tab, turn off **Do profile this data**.\n4. Click **Done**.\n5. Optional: You can add more schedules to specify how certain subsets of your organization data should be profiled. Any data that isn't specified in a schedule is profiled according to the **Catch-all schedule**.\n6. Optional: If needed, edit the catch-all schedule.\n7. Complete the rest of the scan configuration steps.\n\nProfile select projects or data assets in an organization or folder\n-------------------------------------------------------------------\n\nIf you want to profile only a few projects or data assets across an organization\nor folder, follow these steps:\n\n1. Create a scan configuration at the organization or folder level.\n2. In the scan configuration, add a schedule and specify filters that match only the projects or assets that you want to profile.\n3. Specify the frequency and conditions for profiling the data that you selected.\n4. Click **Done**.\n5. Specify that all other data in the organization or folder shouldn't be profiled:\n 1. Go to **Catch-all schedule** , which is the last schedule in the **Schedules** list.\n 2. Turn off **Profile the resources that don't match any custom schedule**.\n6. Complete the rest of the scan configuration steps."]]