Records
The form is the doorway. The record is the point.
Everything a submission becomes after it lands: a card on a board, a status a submitter can track, a number on a shared chart, a conversation with your team, a reference another record points at. This is what “all the things you can do with data records” looks like in practice.
-
One pipeline, four views
The same records as a table, a board, a calendar, or cards. The board’s columns are your workflow’s own states; dragging a card takes the exact move the record page offers, with every server-side guard intact — and a drop the rules withhold says why, right in the column.
-
A tracking link for every record
“Track your request” — a per-record status page showing the stage, reference number and last update, and nothing else. Put {{status_link}} in a confirmation email and every submitter gets the package-tracking experience for whatever they filed.
-
Reports that travel
Share a grouped report as a live read-only page, embed its chart in any site, or schedule it as a daily or weekly email digest to people who never log in. Aggregates only — individual records never leave this way.
-
@mentions that reach people
Type @ in a record’s comments to bring a colleague in: they get the comment by email with a link to the record, and a “Mentioned you” card on their dashboard. Server-checked against membership, capped, and audited like every other write.
-
Records that reference records
A linked-record field holds a reference to a record of another form — orders to customers, inspections to assets. Every link is validated on write: it must exist, be live, and belong to exactly the form the field declares.
-
A portal for the people who filled it in
Submitters track all their records in one place with nothing but their email — a magic link, mailed to the address itself, listing each record’s live status. You choose which field identifies them; everything else stays yours.
-
Forms you can hand to the world
Publish any form’s design as a cloneable template page. Fields, logic and workflow travel; your data, datasets and integrations never do. Anyone who opens the link can make it theirs in one click.
-
Slack cards, not log lines
The Slack integration posts a proper card per event — the record’s name, stage and leading fields, with an “Open record” button back into Faldaro — so a shared channel becomes a live feed of the pipeline.
-
Approvals decided from an inbox
A workflow action mails each approver their own approve/decline link — no account, no login. You choose which move each verdict takes and exactly which fields they see; the decision lands on the record with a name, a comment and a timestamp.
-
A live badge for your README
Any shared count-or-sum report serves a one-number SVG badge off the same link — paste the markdown into a README, a wiki, a docs page, and the number updates with the report.
-
Every share lands harder
Pasted links unfurl as real preview cards (a form’s name, a template’s shape — never a record’s contents), every share dialog offers a printable QR code, a public form can show its response count as social proof, and good templates can be listed — after review — in the community gallery.
Built on the same rules
Public means curated, never exposed
Every outward-facing link here follows the discipline the public form already lives by.
Every shared URL is a 256-bit token — unguessable, revocable by rotating it, and the whole of the link’s authority. Every payload is a curated projection: a status page carries a stage and a timestamp, never answers; a shared report carries aggregates, never rows; a template carries a design, never data. And every refusal looks identical, so probing a link tells you nothing about whether it ever existed.
Questions
Fair questions, straight answers
What exactly does a status link show?
The record’s current stage in your workflow — the label and colour you gave it — its reference number, and when it last moved. Never the answers, never who is working on it, never the rules behind it. You mint the link per record, and revoking it is one click: the old URL stops working everywhere at once.
Can a shared report leak individual submissions?
No. Only grouped reports — counts, sums, averages per category — can be shared or mailed as a digest. A report that lists individual records is refused at sharing time, and if a shared report is later edited into a listing, its public link goes dark rather than serving rows.
Who can be @mentioned?
Members of your organization. Every mention is checked server-side against membership before anything is stored or sent — an id that merely exists proves nothing about whose it is. The mentioned person gets an email with the comment and a link to the record, and a “Mentioned you” card on their dashboard.
How does the submitter portal identify people?
By the one email field you choose, and only that field. A visitor types their address on the public form page; if any submissions match, a secure link is mailed to that address — possession of the mailbox is the credential. An address that merely appears somewhere inside a record never unlocks it, and the page answers identically whether anything matched.
What travels with a shared template?
The design: fields, calculations, show/hide rules, outcomes, and the workflow’s states and moves. Nothing org-local ever leaves — no dataset bindings, no notification templates, no integrations, no records. It is sanitized when you publish, not when someone reads it, so the published copy never held anything private to begin with.
What can an approval link actually do?
Exactly what its author delegated: take the one workflow move named for an approval, optionally another for a decline, and nothing else. The page shows only the fields the author chose, every data-dependent guard still applies at decision time, and a link opened after the record moved on records the verdict without moving anything. The decision — who, when, from where, with what comment — lands on the record’s Approvals tab.
Which plans include all this?
All of it ships on every plan, the Free plan included — sharing a board screenshot, a status link, an approval, a report page or a template must never hit a paywall. Paid plans remove the “Powered by Faldaro” line from public pages and notification emails; the features themselves are not what’s sold.
Put your process on Faldaro today
The Free plan is free forever — unlimited forms, ten thousand submissions a month, and the same builder, logic engine and workflows as every paid plan.
No card required.