Author a rule
Summary
This step completes when you write, test, and save one custom rule. There are two ways to do it: write the rule yourself, or describe what you want in plain language and let the platform draft it for you: the second option is part of the Ultimate plan.
Before you start
The Policies page requires Professional or above. On a lower plan the step shows locked on your checklist, with the caption Not in your plan.
Within Policies you'll work on the Data types tab. Anyone with Policies access can view it; adding or changing data types and detectors needs the Manage Policies permission.
You can have AI draft a detector for you instead of writing a pattern yourself. Describe it in a sentence, inside a data type, comes with the Ultimate plan and is on by default there. Describe a detector, at the top of the Data types tab, is available wherever you can use Policies. If neither is available to you, use the manual editor in step 1 instead.
1. Write the rule
Go to Act → Policies and open the Data types tab. Select New data type and give it a name, a description, and what it counts as. Then, on that data type, either:
- Write it yourself: use Add a detector to pick a kind, then enter a detector name and a pattern (regular expression) or keywords.
- Describe it, and let the platform draft it (Ultimate): select Describe it in a sentence, describe the data you want to catch in plain language, and select Draft a pattern. The platform drafts a pattern for you to review: check the name and pattern, and adjust anything that doesn't match your intent.
Alternatively, use Describe a detector at the top of the Data types tab: say in plain English what to catch and select Draft detector. The draft is listed for you to review, and the detector stays off until it has been reviewed.
2. Save
Save the detector. Nothing is saved until you press Save. The data type joins your Data types list alongside the built-in ones.
3. Test it
Under Try it, paste a sample and select Test (nothing is saved or sent). Try content you expect it to catch, and content you specifically don't want it to catch. Adjust and re-test until both sides behave the way you expect.
Confirm it worked
The new detector appears under How we recognize it on its data type, and the data type's Last 7 days match line begins tracking from this point.
If it didn't work
- Can't find Describe it in a sentence: it's part of the Ultimate plan. On Ultimate it's on unless it has been switched off for your organization: Settings → Organization → Plan & features shows it as Turned off in that case, so ask your account team. Writing the rule manually, or using Describe a detector, doesn't need it.
- Can use Add a detector but not Describe it in a sentence: expected if you're on Professional. It's a plan difference, not a permissions gap; Describe a detector is still available to you.
- Test results don't match what you expect: refine the plain-language description or the sample you provided, rather than editing the underlying pattern directly, and re-test.
- Rule fires too broadly once live: you can disable a rule without deleting it while you refine it further; built-in rules can only be disabled, but a custom rule you authored can be edited or removed entirely.