Overview
A Document Template is the blueprint for a family of Documents — structured, attribute-driven records that always belong to a contact (agreements, applications, certificates). A template defines the document’s attribute schema, how its documents are owned, and whether contacts must authenticate to read them. Every document is created from a template. For the bigger picture, see the Customer Data overview.Where to find it
Document templates live under Customer Data → Document Templates; each template has its own Documents list.Properties
| Property | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Display name of the template. |
slug | string | Yes | Identifier — unique (a–z, 0–9, -); groups the template’s documents. |
description | string | No | Optional description. |
ownership_mode | enum | No | independent (default) or sync_with_contact — see Ownership modes. |
requires_authentication | boolean | No | Whether contact-facing access requires the contact to be authenticated (default on). |
Attribute schema
A template owns the attributes applied to its documents. Unlike Content Templates, there are no versions — attribute values are stored directly on each document.Ownership modes
A template sets how its documents are owned:- Independent (default) — a document’s owner is set on the document itself.
- Sync with contact — documents inherit their contact’s ownership; the owner is read-only on the document and follows the contact. Switching a template to this mode backfills ownership on its existing documents.
Authentication
requires_authentication gates contact-facing access: when on, a contact must be
authenticated to read their own documents (the contact-facing “my documents” flow).
Behaviour & rules
- Type is fixed by the template — every document inherits the template’s attribute schema.
- Renaming a template is safe — references to the template’s documents are kept in sync.
- Bulk documents — a template’s documents can be imported in bulk (see Documents → Seeds).
Seeds
Document templates travel between environments as structural Seeds. Their documents are loaded separately as instance seeds.| Seed type | Supported | Notes |
|---|---|---|
| Structural | Yes | The template and its attributes. |
| Instance | Via documents | Instance seeds target a template’s documents, not the template. |
Governance & permissions
A super admin or Master can create, edit, and delete document templates.API access
Document templates have full CRUD, plus operations to read and set the default workflow and to track ownership-sync progress. See the API reference.Related
Documents
The records created from a template.
Contacts
The contact every document belongs to.
Content Templates
The analogous, versioned content blueprint.
Attributes
The document’s attribute schema.