Composer

Compose new modules without a release.

Visual, multi-tenant builder for QEHS modules. 28 field types, 16 capability blocks, computed fields, lookup lists — no SQL, no scripting, no deploys.

Super-admins author new module templates; tenants configure them to fit their program. Every module is a data model, a form, a list, a detail view, a workflow, and a set of effects — assembled from reusable primitives.

Book a demo See pricing Contact sales

Field block types out of the box

Capability blocks (repeaters, approvals, computed, rollups…)

Lines of custom code to ship a new module

Field blocks — 28 types

Every input you need, validated end-to-end. Simple types are single/multi via a modifier, never separate blocks.

Text, long text, rich text, email, URL, phone, number, currency, percent
Date, datetime, time, date range, duration
Select, radio, checkbox (single/multi via modifier), rating, scale, tag
File, image, signature, drawing, barcode, QR
User, group, location (tree picker + optional geolocation capture)
Lookup list (linked to reusable rows with prefix, color, priority, order)

Capability blocks — 16 types

Behaviours and layout primitives that move beyond simple fields.

Repeater — nested record groups (e.g. inspection items, risk scores)
Computed field — formulas over other fields, recomputed on save
Conditional visibility — show/hide by expression
Linked record — pick-and-embed another module record
Approval, signature, e-sign (W3C VC) — step-up MFA on sensitive transitions
Rollup, aggregate, and cross-module reference
Announcement, rich-text helper, divider, section header

Layout, lists, and detail views

Every module gets form layout, list view, detail view, and dashboards configured in the same Composer.

Sections, columns, tabs, and conditional step layouts
Column picker + saved filters on list views
Kanban, calendar, map (when records have location), and table views
Per-role detail layouts — end-user, approver, auditor
Template diff + selective merge — preview template upgrades before applying

Templates and lookup lists

Compose once, re-use everywhere. Modules and lookup lists are first-class shareable templates.

Module templates — published by the super-admin, installable per tenant
Lookup list templates — fork/extend with locked parent row inheritance
Community marketplace — browse, install, and (on Business+) publish
Sandbox tenants — iterate templates in isolation before promoting to production

Teams replace six-month custom-build programs with a two-to-four-week Composer configuration. Ship your first audit, incident, or permit module without a release.

Composer FAQ

Can I build a new QEHS module without writing code?

Yes. The Composer is a visual, no-code builder — you drag fields, set validation rules, and define workflows in the browser. 28 field types and 16 capability blocks ship out of the box, and a new inspection, audit, or permit module can be live in weeks without a single line of custom code or a release cycle.

How long does it take to configure a new module with the Composer?

Teams typically replace a six-month custom-build program with a two-to-four-week Composer configuration. Because every module is assembled from reusable primitives — data model, form, list, detail view, workflow, and effects — the work is configuration, not development.

Can I share module templates across tenants?

Yes. Super-admins publish module templates that are installable per tenant. Lookup-list templates support fork-and-extend with locked parent-row inheritance, and a community marketplace lets organisations browse, install, and (on Business+) publish templates.

Ready to see Composer?

Pick a slot with our team.

30-minute demo tailored to your QEHS programs and your stack. No slide decks, just a working tenant.

Book a demo Contact sales