Core Concepts
Policy Library
Add your own security policies to BLAZLE. You can ask questions about them in your own words (English, Vietnamese and many more), see which policy a blocked request relates to, and turn any section into a rule written in plain language. Documents are read and stored inside BLAZLE only.
In three steps
- Add a policy. Dashboard → Policy Library → Policies. Upload a PDF, Word (.docx), Markdown, HTML or text file, or paste the text. It is ready in a few seconds.
- Ask. In the Ask tab, type a question such as "Can I send the customer list to my Gmail?". BLAZLE shows the sections that answer it best.
- Make it a rule. Open a policy, pick a section, choose Make this a rule, and add two or three example messages it should catch.
How rules work
- A rule catches messages that mean the same as your examples, in many languages including Vietnamese.
- New rules warn: the message goes through and is recorded. Switch a rule to Block once it behaves as you expect.
- Sensitivity: Strict catches only messages very close to your examples, Balanced suits most rules, Loose also catches looser rewordings.
- Use Try a message in the rule editor to check a rule before turning it on. Nothing is logged or blocked while you try.
- Rules apply to prompts, commands and diffs, and never slow down workspaces without rules.
Related policy on blocked requests
In Intercepts, every blocked request has a Related policy button that shows the three policy sections closest to it.
Limits and access
- Up to 200 documents and 200 rules per workspace, 25 examples per rule.
- Scanned PDFs without selectable text cannot be read: export a PDF with text, or paste it.
- Anyone in the workspace (except Viewers) can read and ask. Adding or changing policies and rules needs Owner, Admin or Security Analyst. Every change is written to the audit log.