Association E-mail Template
What It Is
An association e-mail template gives a workflow its publishable content. Authors work on a draft while sending uses a stable published snapshot. The purpose defines the records and merge fields available to that content, so a template belongs to a particular communication contract rather than being unrestricted HTML pasted into a queue.
Record ownership places composition near the workflow configuration that needs it. For example, an owning record can maintain its own active template without asking staff to locate an unrelated entry in a global template list. Publication still creates immutable content, allowing history to identify what each recipient's message used.
What It Is Not
A template is not a sent message, and a saved draft is not published content. Starter examples do not substitute for the association's publication. Caller-rendered purposes use caller content, while Marketing-owned versions follow their own immutable ownership contract rather than ordinary staff template editing.
How It Is Used
Authors save content, inspect validation findings and publish when it is ready. Preview runs the sending renderer without persistence or delivery. Marked test messages restrict the target to the author or a test mailbox. Record-owned saves preserve omitted fields and publish changed content, while ordinary draft updates use optimistic versions to prevent stale overwrites.
Its Facets
Workflow purpose. A purpose declares the e-mail contract, available records and whether rendering belongs to Platform, the caller or a Marketing version. Determine whether association-authored templates apply.
Editable content. Drafts hold subject, HTML, plain text, display name, reply-to and copy destinations. Allow preparation without changing published sends.
Published snapshot. A numbered immutable version retains the content hash and variable references. Reconstruct the content used for a message.
Record ownership. An owning record, such as an organization type, resolves its template for a purpose. Keep composition associated with the workflow configuration.
Fixed copy recipients. Templates allow up to ten CC and ten BCC addresses each. Apply recurring mailbox copies without bypassing recipient protection.
Publication validation. Checks cover syntax, supported variables, includes, unsafe HTML and reply-to addressing. Prevent invalid drafts from becoming published content.
Author inspection. Preview uses the sending renderer; test delivery marks mail and restricts its destination. Inspect representative rendering before workflow use.
Send readiness. Evaluation reports whether a record or template can send and identifies blocking configuration. Warn before a request enters a blocked outcome.
Marketing-owned snapshot. A Marketing message version owns immutable content outside ordinary staff template lists. Render the pinned Marketing version for its recipients.
How It Relates
A Platform-rendered communication pins the published version selected by its owner or explicit version. The version remains readable after archival. Notification wording belongs to the product's registered definitions, while association templates belong to workflow authors and their purpose contracts.
What It Could Become
The product should establish approval for the later ownership and caller-rendered contracts before design relies on them. Association screens should make unpublished and archived state understandable. A workflow should warn about missing publishable content before submitting mail that can only end as configuration blocked.