Org:Mindful Goat Playground
After completing this unit, you'll be able to:
You've learned about the power of Data Detect for identifying sensitive data across your Salesforce org. Now it's time to put that knowledge into action by creating your own data detect policy.
In this unit, you create a data detect policy, add detection rules, configure the scan scope, run the policy, and review the results. By the end, you'll have a working policy that identifies sensitive data patterns in your org.
Before you start, make sure you have a Trailhead Playground ready. If you need to create one, follow the instructions in Trailhead Playground Management.
This hands-on challenge requires the following prerequisites:
A data detect policy is a container that groups your detection rules and scan configurations together. Think of it as a project that defines what sensitive data to look for and where to look.
Follow these steps to create your first policy.
Sensitive PII Detection.Scans org data for personally identifiable information including SSN, email, and phone patterns.
Detection rules define the sensitive data patterns your policy looks for. Each rule targets a specific type of data, like Social Security numbers, email addresses, or credit card numbers, using pattern matching.
Add three detection rules to your policy.
SSN Pattern.\b\d{3}-\d{2}-\d{4}\bEmail Pattern.Phone Pattern.You should now see three rules listed on the Detection Rules tab. Each rule shows its name, detection type, and sensitivity level.
The scan scope tells Data Detect which objects and fields to scan. Rather than scanning everything in your org (which can take a long time), you target specific objects where sensitive data is most likely to live.
Configure the scan scope for your policy.
Now that your policy has detection rules and a scan scope, you're ready to activate and run it. When you run the policy, Data Detect scans the configured objects and fields for matches against your detection rules.

After the scan completes, Data Detect presents the findings in a results dashboard. You can see how many matches were found, broken down by detection rule, object, and sensitivity level.
Review your scan results.
If any rule shows zero matches, that's expected. It means your org's sample data doesn't contain that pattern. The important thing is that your policy ran successfully and produced a results report.