Form Settings

Form Settings

Every form in NexusRMS has its own configuration panel where you control how the form behaves, who receives notifications, how submissions are processed, and what submitters see after completing the form. These are per-form settings — each form is configured independently.

General Settings

• Form Name — the internal name used to identify the form within NexusRMS.
• Slug — the URL-friendly identifier used in the form's public link.
• Description — an optional summary of the form's purpose, visible to administrators.
• Status — controls the form's lifecycle. Options are Draft (not visible to the public), Published (accepting submissions), and Archived (read-only, no longer accepting submissions).

Submission Settings

• Enable/Disable Submissions — toggle whether the form accepts new submissions.
• Submission Limit — set a maximum number of submissions. Once reached, the form stops accepting responses.
• Close Date — specify a date and time after which the form automatically stops accepting submissions.

Notification Settings

• Submitter Confirmation — enable to send an automatic receipt email to the person who submitted the form.
• Team Notification — enable to alert team members when a new submission arrives.
• Recipient List — add one or more email addresses to receive team notifications.

Branding Settings

• Logo — upload a company logo displayed at the top of the form.
• Colours — set the primary colour and background colour using hex values.
• Font — choose a web-safe font family for the form text.
• Custom CSS — inject custom styles for advanced visual control.

Record Mapping Settings

• Auto-Create Rules — configure which records are automatically created from form submissions (e.g. client, project, quote).
• Field Mappings — map form fields to the corresponding fields on the target record.
• Duplicate Detection — choose how to handle submissions that match existing records.

Webhook Settings

• Webhook Endpoints — add, edit, or delete webhook URLs that receive submission data.
• Conditional Triggers — configure rules that determine when a webhook fires.
• Delivery Logs — review the status of past webhook deliveries for troubleshooting.

Analytics Settings

• Enable/Disable Tracking — toggle whether form views, submissions, and conversion events are tracked.

Conditional Logic

• Field Visibility Rules — configure conditions that show or hide fields based on the values of other fields.

Access Control

Published forms are public by default — anyone with the form URL can submit a response. This is the standard behaviour for lead-capture forms, enquiry forms, and other external-facing use cases.

Confirmation Page

Customise the thank-you message displayed to submitters after they complete the form. Use this to confirm receipt, provide next steps, or share contact information for follow-up enquiries.

Redirect URL

Optionally redirect submitters to an external page after submission instead of showing the default confirmation page. This is useful for directing submitters to a specific landing page, booking calendar, or resource on your website.

Form Permissions

Only CoreAdmin users and designated power users have permission to create and manage forms. This ensures that form configuration — including notifications, webhooks, and record mappings — is controlled by authorised personnel.

Tips

• Review all settings before publishing — check notifications, branding, webhooks, and record mappings to ensure everything is configured correctly.
• Test end-to-end — submit a test response and verify that notifications are delivered, webhooks fire, and records are created as expected.
• Use the close date feature for time-limited campaigns or event registration forms.
• Set a submission limit to prevent oversubscription for capacity-restricted events.