Folders, visibility and compliance controls
This page covers two jobs: keeping a large Template Library tidy, and locking down a sensitive template so only the right people, records and formats are involved. These limits apply everywhere a document can be generated.
Template folders
Section titled “Template folders”Use folders to keep a growing library easy to find your way around, especially when several teams share it.

- Create a folder: click + New above the folder list, type a folder path such as
Sales/Quotes, and save. A/makes a folder inside a folder. - Rename or delete a folder: use the folder’s actions menu.
- Move a template: click Move to folder on the template’s card and pick a folder.
Templates not in any folder appear under Uncategorized. All templates shows everything at once.
When you import a template that sits in a folder, that folder is created for you in the target org. See Export and import.
Control who and what a template is for
Section titled “Control who and what a template is for”These three controls apply everywhere a document can be made: the record page, batches, Flow and list views.

| Control | What it does |
|---|---|
| Visibility | Shows the template only to users with the permission sets you choose. Board packs, HR letters or executive versions stay out of everyone else’s list. Admins still see every template in the editor. |
| Specific records | Limits the template to a chosen set of records. It only appears for, and only generates for, those records. A batch run skips records outside the set instead of failing. |
| One output format | Tick a single format on the version’s Formats this version makes card. For example, a signed contract can then never be generated as an editable Word document. A request for the other format is refused. See Word output. |
Note: if a user cannot access a bundle, it is simply left out of their list on the record page. The rest of the generator still loads normally.
Related compliance settings
Section titled “Related compliance settings”Two more per-template settings usually belong to your compliance team rather than the template author: the audit log, which keeps a fingerprinted record of every generation, and the retention window, which deletes old files. Both are covered in Compliance: access, audit log and retention.