Documents

A structured record created from a Document Template — always tied to a contact, with attributes, ownership, and archive, but no versions.

Overview

A Document is a concrete record created from a Document Template — an agreement, application, or certificate. Every document belongs to a contact and inherits the template’s attribute schema. Unlike Content Instances, documents have no versions — attribute values are stored directly on the record. For the bigger picture, see the Customer Data overview.

Where to find it

Documents are listed under each template’s Documents list, in Customer Data → Document Templates. Contacts read their own documents through the contact-facing “my documents” flow.

Properties

Property	Type	Required	Description
title	string	Yes	Display name of the document.
slug	string	Yes	Identifier.
template_id	reference	Yes	The template this document is built from.
contact_id	reference	Yes	The owner contact — every document belongs to one.
parent_id	reference	No	An optional parent document.
(attribute values)	mixed	—	The document’s content, validated against the template’s attributes.

Documents also support taxonomies, tags, relationships, workflows, and archive.

Ownership

A document’s owner follows its template’s ownership mode:

• Independent — set the owner on the document.
• Sync with contact — the owner is read-only and follows the document’s contact.

Behaviour & rules

• Every document belongs to a contact — contact_id is required and ties the document to one contact.
• No versions — attribute values live directly on the document (simpler than content instances).
• Archive, don’t hard-delete — documents use Archive and can be restored.

Seeds

Documents are loaded in bulk as instance Seeds into a single template’s documents — a direct import for small batches, or an asynchronous upload for large volumes. The template itself travels as a structural seed.

Governance & permissions

A super admin or Master can manage any document. Documents carry Ownership — directly or synced from the contact — so a Journey Manager manages the documents they own.

API access

Documents have full CRUD (scoped by template) plus restore and relationships. Contacts read their own documents through the Contact API. See the API reference.

Related

Document Templates

The blueprint a document is created from.

Contacts

The contact every document belongs to.

Ownership

Independent vs synced ownership.