Folders, visibility and compliance controls

Two separate jobs live on this page: keeping a large library navigable, and restricting a sensitive template so that only the right people, records and formats are ever involved. The restrictions apply across every generation path.

Template folders

The Template Library supports folders, so a library that has grown across several teams stays easy to navigate. Create, rename and delete folders, and move templates between them. Unfiled templates appear under an “Uncategorised” view, and an “All templates” view still shows everything at once.

Folder paths referenced by an imported template are created automatically in the target org. See Export and import.

Template-level access controls

Three controls apply across every generation path: record page, batch, Flow and list view.

Control	What it does
Audience visibility	Restricts a template to users who hold the right permission sets, so sensitive templates such as board packs, HR letters or executive variants stay out of everyone else’s picker. Admins still see every template in the editor.
Per-record targeting	Scopes a template to a specific set of records, so it only appears, and only generates, for those records. Batch runs filter to the records in scope automatically rather than failing outright.
Output-format lock	Locks a template to a single output format, so, for example, a signed contract cannot be generated as an editable Word document.

Note: a bundle a user has no access to is simply left out of their list on the record page, rather than stopping the generator card from loading.

Two further per-template settings sit with the compliance team rather than the template author: the fingerprinted audit log, and the retention window that deletes aged files. Both are covered in Compliance: access, audit log and retention.