Elementary Interactive

Forms and events

A form that emails its submissions is a form that loses them. Registrations counted by hand are registrations counted twice.

Forms are where personal data enters your organisation. That makes them the most compliance-critical part of a content platform — and the part most systems treat as an afterthought.

Building a form

Forms are built from the same field library the rest of the platform uses, which is why they behave predictably.

One field set, two places

The same central field library serves both internal data structures and public forms. A field type is built once and behaves identically in both, with the same validation rules.

Conditional logic

Show or hide fields based on previous answers. Forms that adapt to what the visitor has already told you, instead of asking everything of everyone.

No third-party gatekeeper

Spam is handled with delayed loading and a honeypot field. No data is passed to a third party, and no verification step is imposed on the visitor.

Forms are content

Every form can be published, scheduled and expired like any other content, with its own permissions and its own audit trail.

Where a submission goes

A submission is stored as a record, not sent as an email and forgotten. From there it can be routed to the right people, trigger a notification, or create a record in another part of the system.

That hand-off is where this layer ends and the process layer begins. If what follows a submission is an approval chain, a handover or a multi-step internal process, that is Nitrogen Works — a separate module with its own workflow engine. Forms don't depend on it, and it doesn't depend on forms.

Events

Registration, ticketing and attendee communication, with the attendee list as data rather than a spreadsheet.

Complete lifecycle

Create, promote, manage and analyse — from first announcement to post-event reporting. Nothing falls through the cracks between tools.

Registration and check-in

Online registration with capacity limits and waitlists. On-site check-in for entry management, and real-time attendance tracking.

Automated communications

Scheduled reminders, confirmations and follow-ups, by email or SMS. Set once, and the system handles the rest.

What happens to the data

The part that matters when an auditor asks.

Each form field can be marked as containing sensitive data: marked fields are masked in the interface, visible only to authorised data owners. Email addresses are masked by default.

Forms can be assigned dedicated data owners — the only users who can export submissions. Exports are password-protected, non-editable files, with the password set by the data owner at the time of download.

Every form can purge its collected data automatically after a defined period, calculated from the form's expiry date. No forgotten datasets sitting in a database years after an event.

GDPR compliance

The rest of the content layer.

Nitrogen Content

When a submission starts a process.

Nitrogen Works