Getting started

Five steps from an empty organisation to a form collecting real submissions. The dashboard keeps a checklist of its own alongside these — first form, first link, first submission, first teammate, first integration — each ticked off from what actually exists rather than from anything you mark done.

1. Create your organisation

Sign up with a name, an email and the organisation's name. The organisation is the boundary everything else lives inside: every form, submission and file belongs to it, and the database itself enforces that separation — a query from one organisation cannot see another's rows.

2. Make a folder, then a form

Folders are the sections of your app — an insurer makes Policies and Claims, a support desk makes Tickets. Nothing in Faldaro assumes a domain; the vocabulary is yours. Inside a folder, create a form: start from one of the twelve templates, import a template file, or begin empty.

The fastest path is the assistant. Press Build with AI, say what you want to collect, and it creates the folder, the form and the fields — with exactly your permissions, never more — as an editable draft.

3. Design and publish

The builder edits a draft. Publishing makes that draft the live version and freezes it: submissions keep the definition they were filled against forever, and editing a live form starts a new draft rather than rewriting history. Publishing also validates everything — formulas that cannot compute, workflows that cannot be exited, patterns that cannot compile are refused with the reason, not discovered by a submitter.

A form is never reachable anonymously just because it exists. Someone with the publish privilege issues a link: an unguessable token that renders the form to anyone who holds it. Rotate the link and the old URL stops working — the recovery for a link that spread too far.

5. Watch submissions arrive

Each submission is a record: it carries the data, every value the server computed, and — if the form has a workflow — a state that people with the right privilege move it through. Reports, notifications, documents and integrations all hang off that record.

Where to go next

Core concepts is the ten-minute map of everything below — worth reading once before you build in earnest. After that, follow whichever your work needs:

Formulas & logic — totals the server owns, and everything else a rule can do.
Workflows — draw the states and moves from draft to done, audited, with deadlines that fire themselves.
Submissions — finding, assigning and importing the records you collect.
Notifications and documents — the email and the paperwork.
Payments — charge for what the form collects, priced on the server.
Reports — ask questions where the answers already live.
Users & roles — bring your team in and decide what each can do.