India Audit Lens
Create, preview, and reset email templates
Create or customise a reusable email subject/body, insert only supported merge fields, preview with synthetic values, and safely reset a system-derived template or delete a firm-owned template.
By India Audit Lens product team · Updated 2026-07-17
Find the right template
Navigate to Settings → Integrations → Email Templates. Search by template name or use the category filter. Review template name, category/type, active/default/custom state, and available actions. Identify the product event that consumes the template before editing it.
Create or edit
Click New Template, or click Edit beside the intended template. Enter a unique Template name. Enter the Subject line. Edit the message body with the provided rich-text/source control. Use Insert field and the searchable merge-field list to insert a supported token such as the visible {{ username }} style. Do not type an invented variable or copy single-brace tokens from Document Templates; the email engine uses its own supported merge-field syntax. Review links, salutations, fallback wording, privacy, and mobile-length subject.
Preview and test variables
Click Preview. Confirm the preview opens without check template syntax errors. Verify every merge field is replaced with the synthetic preview value and no raw {{ ... }} remains. Test long names, optional/missing values, special characters, multiple links, and narrow width. Save and wait for Template created or Template saved. Trigger the event only in a synthetic/test workflow and send to an internal test address before client use.
A successful editor preview does not prove SMTP delivery or the final event context. Test both the template and the sending workflow.
Reset or delete safely
Reset to default removes the firm's customisation from a resettable system template. Confirm the exact template and re-preview the restored content. Delete removes a firm-owned template. Confirm no active event depends on it and that another approved/default template will be selected. To preserve a prior approved version, copy its controlled content/reference outside the editor or create a new version-named firm template before the destructive action; the page does not expose a full publish/archive version lifecycle.
Expected result
The correct event selects an approved active template, every supported merge field resolves from the event context, the email renders correctly, and reset/delete actions do not leave a sending event without an intended template.