Survey forms
Design a survey once. Let every module ask it.
A survey, form and exam engine any other module can plug into — authored visually, answered by logged-in users or anonymous visitors, and scored on the server.
- 5
- Lifecycle steps
- 2
- Respondent types
- 0
- Exam limits forced on you
Author visually
Administrators build surveys, questionnaires and scored exams in a licensed drag-and-drop designer — no code, no developer in the loop.
- Drag-and-drop authoring with pages, question types and logic
- Scored exams alongside plain surveys and forms
- Every exam control is a per-survey setting the author toggles: time limits, attempt caps, question and answer shuffling, pass thresholds
- Defaults are permissive — the platform never forces a limitation
Image slot — asset to come
Screenshot: the designer's question toolbox and a page being edited.
Ask anyone
A survey can be answered by a logged-in tenant user or by an anonymous visitor through a token-protected public link — both are designed in from day one.
- Authenticated runs tied to the tenant user who answered
- Anonymous runs through public, token-protected links
- One lifecycle for every use: author, embed, run, submit and score, reuse
Image slot — asset to come
Screenshot: a survey being filled in by a respondent.
Any module can plug in
The engine is a platform capability, not a feature bolted onto one workflow. Other modules discover surveys, present them, and gate their own steps on the result — without the survey module knowing they exist.
- Stable host-owned contracts for discovering and presenting surveys
- Gate a step on completion or on a pass score
- Read results back from the module that asked
Image slot — asset to come
Screenshot: a survey embedded inside another module's page.
Results, scores and retakes
Every answer and score is stored. Respondents see their own results; admins review all of them.
- Respondents see their answers, their score and pass or fail
- Exams can be retaken, subject to the author's attempt settings
- Admins review every response in one place
- Scoring runs on the server, never in the browser
Image slot — asset to come
Screenshot: a respondent's results view with score and pass state.
Tenant-private by design
Each tenant designs and sees only its own surveys. There is no cross-tenant template library — deliberately.
- Surveys, answers and scores live in the tenant's own space
- The host designs host-scope surveys only for its own use
- A few private starter copies can be seeded on install — never shared
Worth knowing: There is no cross-tenant template library, on purpose: one tenant's surveys are never visible to another.
What every module inherits.
- Installs from the marketplace with no redeploy — the menu and the permission list update immediately.
- Creates its own tables, in its own schema, inside that customer's database.
- Packages are cryptographically signed when they are built, and the signature is checked before the host unpacks one.
- Uninstall switches a module off and keeps its data. Dropping the tables is a separate, deliberate choice.
Works with
Want to see Survey forms running?
Thirty minutes, a live workspace, and an honest answer about what each module does and doesn't do yet. Missing a module? A custom build is a fixed-scope project, from €25.000.
Book a call