Forms are standalone pages that ask questions and record the answers: an enquiry form, a project brief, an onboarding questionnaire, a survey. Each form lives at its own public link, /forms/your-form, on your portal domain. Forms ask questions; they don't sell. Selling happens on service pages (see Checkout and payments).

Forms is an optional module. Turn it on or off in Settings → Modules.

Where it lives#

What	Menu path	Route
All forms	Store → Forms	/forms
A new form	Store → Forms → New form	/forms/new
A form's results	Click a form	/forms/FORM-ID
The editor	Edit form on the form's page	/forms/FORM-ID/edit
The public form	Your portal domain	/forms/your-form

The editor has tabs: Fields, Rules, Scripts and Configuration.

Create a form#

1. Go to Store → Forms and click New form.
2. Give the form a name. A new form starts with Name, Email and a "How can we help?" question.
3. Optionally add Form information: text shown above the first question.
4. Add fields from the palette (see the table below), then click a field to edit it.
5. Set up Rules and Configuration if you need them.
6. Choose a status in the status widget and click its button, such as Save & publish.

The Fields tab saves as you work. Publishing never happens on its own: you pick a status and click its button. The button saves anything still pending first, so what goes live is what's on screen.

Field types#

The palette groups fields into three sets.

Client profile#

Field	What it collects
Name	The person's name. Every form has it.
Email	Their email address. Every form has it.
Phone	A phone number.
Address	A postal address.
Email opt-in	A tick box for marketing consent, such as "Send me occasional news and offers".

Each client profile field can be used once per form.

Project data#

Field	What it collects
Text	A short answer.
Long text	A longer answer.
Number	A number.
Website	A web address.
Date	A date.
Checkbox	A single tick, such as "I agree".
Option group	One choice, with every option shown.
Dropdown	One choice from a list.
Hidden	A value the visitor never sees, stored with every submission.

Utilities#

Field	What it does
Section break	A heading and subheading that split the form into sections.
Page break	Starts a new page, making the form multi-page. Set its Next button label.
Content	A block of text with bold, italic, links, headings and lists.

Field settings#

Click a field to edit it. Depending on the type you can set:

• the field name and Help text
• a Placeholder
• Options for an option group or dropdown
• Required field
• Prefill from the URL: name a parameter, and a link like ?company=Acme fills the field in
• for a Hidden field, a fixed Value or Read from the URL, for example utm_source

Use the icons on each field to drag it, move it up or down, duplicate it or delete it.

Hidden fields that read utm_source, utm_medium and utm_campaign are the simplest way to see which campaign each submission came from.

Rules#

Rules show or hide fields based on earlier answers. Open the Rules tab.

1. Add a rule and choose whether it needs all of these or any of these conditions.
2. For each condition, Choose a field and the value to match (for a checkbox, checked or unchecked).
3. Under Then, choose Show or Hide, and Choose fields.
4. Click Save rules.

With no rules, every field is always shown. A required field that a rule hides isn't required while it's hidden. If you delete a field, it's removed from any rule that mentioned it.

Configuration#

Section	Setting	What it does
Link	Form link	Where the form lives. The link only works once the form is published.
After submitting	Button label	The submit button's text.
	Thank-you message	Shown in place of the form once it's sent.
	Redirect instead	A full https address to send the visitor to instead of the message.
Email each submission	Send to your team	Emails and notifies everyone whose role can see forms.
	Also send to	Any other inboxes, even without an account. They get the answers but no admin link.

Replying to a submission email answers the person who sent the form.

Statuses#

Status	Who can open it
Draft	Only your team can see it.
Private	Only signed-in clients can open and send it.
Public	Anyone with the link can open and send it.
Archived	Taken down and kept. Nobody can open it; every answer stays.

A form that has submissions can't be deleted, only archived. A form nobody has submitted can be deleted. You can also duplicate a form from its actions menu.

Read submissions#

Open a form from Store → Forms to see:

• Submissions since the form was made, the Last 7 days and the Last submission
• who submissions are Emailed to
• a chart of Submissions, last 30 days
• every submission, with Show answers to expand one

The forms list shows each form's number of questions, submissions and last update, and you can sort by Most used.

Send an onboarding form to a client#

You can send a published form to one specific client, so their answers are filed on their record.

1. Open the client from Work → Clients.
2. From the actions menu, choose Send an onboarding form.
3. Pick the Form and send it.

The client gets an email (and a notification in their portal) with a link that is theirs. What they send back appears on their client page under Forms. If email can't be sent, ClientOS opens a support conversation for them with the link instead. You can also copy the link and send it yourself; answers through the plain link aren't filed on anyone.

Sending needs permission to edit clients.

Spam protection#

Once Cloudflare Turnstile is connected in Settings → Integrations, every public form asks for the check before a submission is saved. See Checkout and payments.

Tracking#

With the Traffic tracking module on, visits to each form are recorded with where they came from, and Submitted the form counts as a conversion. You can make a tracking link that goes to a form. See Leads and tracking.

Not available#

Forms don't offer file upload, signature or secret-text fields, and you can't add your own scripts. The Scripts tab explains why and points to hidden fields for attribution.

What the client sees#

• A branded page at /forms/your-form, on one page or several.
• The thank-you message or your redirect after sending.
• For a private form, a sign-in first.

Permissions#

Permission	Lets someone
See forms	Open forms and their submissions, and receive submission emails when Send to your team is on.
Build a form	Create forms.
Edit a form	Change fields, rules and configuration.
Publish or unpublish a form	Change a form's status.
Delete a form	Delete forms with no submissions.

Tips#

• Keep forms short. Use rules to show follow-up questions only to people who need them.
• Use Private for client-only questionnaires, and Send an onboarding form when you want answers filed on a specific client.
• Use a redirect to a thank-you page on your own site if you track conversions there.
• Archive old forms rather than deleting them, so past answers stay readable.