The Forms module in Sygnal allows authorised users to configure structured, role-based forms used across Clients, Staff, Incidents, and Compliance workflows. Forms are configurable, version-controlled, and can be published with optional print templates.
Access & Permissions
Who can access the Forms module?
Only users with the relevant permission can access the Forms module in Sygnal Web.
Form Types & Visibility
What types of forms can be created?
When creating a form, users must select one of the following form categories:
Client Documents
NDIS Agreements
HR Documents
RFI Forms
Incident Primary
Where are these forms used and visible?
| Form Type | Visibility |
|---|---|
| Client Documents | Client Profile |
| NDIS Agreements | Client Profile |
| HR Documents | Staff Profile |
| RFI Forms | Staff Profile |
| Incident Primary | Incident Module |
Creating a Form – Step-by-Step Guide
Step 1: Create a new form
Navigate to Forms module
Click Create
Select the required Form Type
Step 2: Define the form name
Enter a Form Name relevant to the selected type
Example: If creating an Incident form → enter the Incident Form Name
Step 3: Create form sections
Forms are built section by section.
Example:
General Information
Incident Details
Reporting Details
Each section:
Is created independently
Represents a logical grouping of data
Step 4: Configure section access (user roles)
For each section, the user must define:
Which user role levels can access or complete that section
This controls visibility and edit access per section.
Step 5: Add parameters (form fields)
Within each section, click Add New to define parameters.
Supported component types include:
Text
Text Area
Date Picker
Birthday Picker
Signature
Single Choice
Multiple Selection
Statement Upload
Grid
Address Picker
Attachment
Image Upload
Step 6: Configure parameter behaviour
For each parameter, users can:
Set mandatory / optional
Define display order
Configure column headers (where applicable)
Delete parameters or sections before saving
Step 7: Save and publish the form
Once all sections and parameters are configured:
Click Save
Publish the form to make it available in the system
Print Template Setup (Optional)
When is a print template required?
If the captured form data needs to be printed or exported, a print template must be created.
How to create a print template
Click the Template icon on the form
Enter a Template Name
Multiple templates can exist per form
Open the Print Design view
Designing the print layout
Copy and paste the desired layout from:
Word
PDF
Click Select Parameter
All previously created form parameters will be listed:
Grouped by section
Identified by parameter name and index
Map the parameters to the required positions in the layout.
Can print templates be edited later?
Yes. Print templates:
Can be edited at any time
Do not require form re-publication
Form Versioning & Lifecycle
Can a published form be edited?
No. Once a form is published:
Core structure (sections and parameters) cannot be edited
To make changes, you must copy the form or create a new version
How does form copy and versioning work?
From the main Forms view:
You can copy an existing form
If the copied form uses the same name, it will be created as:
Form Name – V2The previous version is automatically retired
If a new name is used, the form is created as V1
Can a form be expired?
Yes.
Forms can be expired
Expired forms are no longer available for use
Expired or published forms cannot be structurally edited
What can be changed after publishing?
Even after publishing, users can:
Modify section-level action user roles
This does not require creating a new version
FAQ – Common Questions
Can I edit a form after publishing?
No. Structural changes require copying the form or creating a new version.
Can I reuse an existing form as a base?
Yes. Use the Copy option to create a new version or new form.
Can one form have multiple print templates?
Yes. Multiple templates can be created and maintained per form.
Are form parameters reusable across sections?
Parameters are unique per section but can be recreated across sections if needed.
Where are Incident Primary forms used?
Incident Primary forms define the structure of forms used within the Incident module.
Do forms support role-based access?
Yes. Access can be controlled per section based on user role levels.