Templates

A template captures how you handled a document as a set of reusable rules, so you can apply the same treatment to a different-but-similar document. Edit one invoice the way you want — keep the company name, synthesize every person, redact the stamp — save it as a template, and the next invoice gets the same logic in one click.

Templates live in the editor’s toolbar: a dropdown to apply one, and a save button to make one from your current edits.

The problem they solve

You process the same shapes of document over and over: monthly invoices on one layout, CVs in one format, claim letters from one insurer. Each time, you make the same editing decisions — the same fields to keep, the same fields to synthesize, the same region to black out. A template records those decisions so you don’t redo them per file.

What a template is (and isn’t)

A template is not a fixed set of values. It doesn’t say “replace Acme with Globex” — that’s a dictionary. A template captures rules about kinds of things:

• “keep this specific value” (the company name you turned off)
• “synthesize every NAME”
• “redact every ID”
• and a default for everything else

So it generalizes to documents it’s never seen, as long as they’re the same shape. The detail is in how rules generalize.

Templates vs. dictionaries vs. profiles

Three reuse tools, three jobs:

Tool	Reuses	Best for
Profile	A whole anonymization configuration (mode, prompts, fields)	Picking an approach before a run
Dictionary	Exact value → value pairs	Keeping identities consistent across runs
Template	Per-type and per-value rules from your editing	Re-applying hand edits to similar documents

They compose: run with a profile, edit in the editor, save a template of your edits, and keep a dictionary so the fakes stay stable.

In this section

• Saving a template — from your editor edits
• Applying a template — to another document
• How template rules generalize — keep / by-type / default
• Template recipes — invoice, CV, contract

Next

• Saving a template