Extend Bolt

Detectors.

Teach masking to recognise your own identifiers before anything reaches an AI model. Admin only, tier 2: a detector changes what Bolt sends.

Two kinds of recognizing.

A launcher recognizer is part of a User App. It notices text you paste and offers the App. It never changes masking, and anyone can add one.

A detector changes masking for everyone in your organization, so only an admin can add one. The rest of this page is about detectors.

Ways to add a detector.

Kind	What it is	Where
Custom pattern	A regular expression and the kind of identifier it finds, with an optional checksum.	Settings → Admin → Security & Compliance → Custom Regex Patterns
Pack recognizer	A pattern inside a catalog or compliance pack, with context words, checksum and what to do on a match.	In a pack; see Compliance packs
Imported rules	Bring sensitive-information types from Microsoft Purview, keyword dictionaries from Forcepoint, or rules from a Bolt pack.	The admin API `/api/v1/admin/dlp/rule-imports`; there is no Settings screen for it yet
Exact records (EDM)	Your own records, such as an employee list. Bolt reads the file where it is and matches the combinations you name; the records never enter the pack.	The `edm:` block of a pack

Pack recognizer fields.

Field	Meaning
`id`, `title`, `pattern`, `flags`	The pattern and its name.
`entityType`, `family`	What it finds.
`context`	Words that must appear within 60 characters of a match before it is masked. Use it for shapes that look like ordinary numbers.
`checksum`	Reject look-alikes: `luhn`, `iso7064`, `verhoeff`, `mod11` or `none`.
`governance`	`mask` or `block_llm` make it part of masking. `none` only recognises it in the launcher.

In a catalog pack

recognizers:
  - id: acme-employee-id
    title: Acme employee ID
    pattern: '\bAE-\d{6}\b'
    entityType: EMPLOYEE_ID
    context: [employee, staff, badge]
    governance: mask