Navigate the Form Template Workspace

Overview

When you open a form template, you land in a workspace with four tabs running along the top: Details, Actions, Template, and Custom HTML/Javascript. Each tab is a distinct area of configuration — understanding what lives where makes building and maintaining forms a lot faster.

‍

Details

The Details tab is the starting point for any form. It holds the core settings that define what the form is, who can access it, and how it behaves.

‍

Edit form

The basic identity of the form — its Name, Code, Category, and whether it's Enabled. The View form link opens the live published form directly, so you can quickly check how it looks to users without leaving the workspace.

‍

Access and Authentication

Controls how users reach the form and what they need to do to access it. Settings here cover the access mode (Public or Private/API), authentication method, SMS and email MFA, and Chandler Verify KYC mode and policy. If a form is set to Private and delivered via an outbound CX Platform link, pre-filled data can be validated against the authenticated user here.

‍

Prefill Data Settings

Controls whether pre-populated field data is shown before the user has authenticated. You can require authentication, MFA, or KYC to be completed before prefilled data is revealed — useful for forms containing personal or financial data that shouldn't be visible until identity is confirmed.

‍

Save and Resume

Enables users to save a partially completed form and return to it later. Options here include save via link copy, save via email, password protection on resume, and whether to re-run authentication, MFA, or KYC when the user resumes. See the Configure Save and Resume guide for full details.

‍

‍Saving changes in Details: Click Update at the bottom of the Details tab to save any changes. Changes here don't require a re-publish — they take effect as soon as you save.

‍

Actions

The Actions tab is where you set up automated triggers that fire when a form event occurs — such as a submission, a save, or an expiry. Each action can send a CX Platform communication, call a Webhook, or post to an Azure Message Queue.

When a form has no actions configured, the tab displays "No actions defined." Click + Add new to create the first one. A form can have multiple actions on the same or different status events. See the Add Actions to a Form guide for full setup details.

‍

Template

The Template tab is where you build the form itself. It contains four sub-views accessible from the secondary tab bar beneath the main tabs.

View	What it's for
Form Designer	The drag-and-drop canvas for building the form. Includes the Toolbox of question types, page management, Form Settings, and Options. Toggle between Simple mode and Advanced mode — Advanced mode unlocks Form Logic and the JSON Editor.
Test Form	A live preview of the form. Use this to check the layout, test logic rules, and verify completion messages before publishing.
Form Logic	A centralised view of all conditional logic rules on the form — conditions and the actions they trigger. Available in Advanced mode only.
JSON Editor	A direct view of the form's underlying JSON structure. For advanced users who need to inspect or edit the form definition at the code level.

‍

Use Save to save a draft of your form design without making it live. Use Publish to push the current version live for users.

‍

Custom HTML / JavaScript

The Custom HTML/Javascript tab gives you four code editors for template-level customisation. Code entered here only applies to this specific form — it doesn't affect other templates or your tenant's global defaults.

Section	What it does
Custom CSS	Injected inside a `<style>` tag in the HTML header. Use this for template-specific styling — fonts, colours, spacing, button styles, and responsive rules. Enter CSS only; no `<style>` tags needed.
Custom Header	Injected inside the `<head>` tag of the page. Use this to link external CSS files, load web fonts, or add metadata and custom favicons specific to this form.
Custom Footer	Injected at the end of the form, above any custom JavaScript. Use this for footer branding, analytics tracking pixels, or links to external JS files. Third-party libraries should be hosted within the CX Send module rather than linked externally.
Custom Javascript	Injected inside a `<script>` tag in the HTML footer as the last item. Use this for client-side validators, minor UI behaviour, or analytics event handlers. Enter JavaScript only; no `<script>` tags needed.

‍

Click Update to save changes, then Publish to make the updated template live.

‍

Each tab handles a distinct part of a form's configuration — Details for identity and access, Actions for automation, Template for the form itself, and Custom HTML/Javascript for styling and scripting. Once you know where each setting lives, you'll spend a lot less time hunting around.

‍