Help CenterDocuments & quotesLook it up
Who can design templates, and print and save documents
Template permissions decide who designs and who prints. Printing also respects your permission on the record and on the linked units.
How it works
The classic designer has its own permissions, with the same names.
The document reads the record within your scope (Allowed, Team-wide access, If responsible). A record outside your scope shows as if it doesn’t exist. Fields from a linked unit you can’t read print empty. See Permissions: Allowed, Team-wide access, If responsible, Denied.
Set the permissions in roles.
At a glance
Task
You need
See templates, print and download
The permission to read document templates + view the record
Create a template
The permission to create document templates
Edit a template
The permission to edit document templates
Delete a template
The permission to delete document templates
Save to the record
Read templates + the permission to edit the unit’s records + the record within your scope + edit this record
Design with AI
Create or edit templates + credit
Generate from an automation
Prints with the permissions of the person who created the automation
A real example
Basma Clinics
The situation
Reception staff changed templates by mistake.
What they did
- A “Reception” role: read document templates only.
- A “Management” role: create, edit and delete.
The result
Reception prints and saves, and only management changes the design.
A made-up company, to show the idea. The numbers are rounded.
Did this guide solve it?
If not, we’ll ask what was missing.