How to build a form, get it onto a field agent device, route what comes back through approvals, and read the result. Search the topics below, or send the question straight to the team.
Eight areas, matching how the product is actually organised. Each one lists what it covers so you can tell whether your question belongs there before you ask it.
For new administrators.
The first hour: getting your organisation set up, adding the people who will build and the people who will collect, and putting one real form in a field agent hand.
For form builders and process owners.
Everything in the builder: the page, section and question hierarchy, the 28 question types, and the rules that make a long form behave like a short one.
For supervisors and planners.
How a form becomes a job on somebody device: who gets it, when, with what already filled in, and what happens when nobody accepts.
For field agents and the people supporting them.
What the app does with no signal, what it does when signal comes back, and the capture features that only exist on a device.
For process owners and approvers.
What happens after submit. Design the path on a canvas, park a run on an approval, escalate it when nobody moves, and bounce it back for correction.
For iT and integration engineers.
Moving data in and out. Push a finished submission into your systems, or read from them mid-form while the agent is still standing there.
For analysts and operations managers.
Reading what came back. Standard dashboards, exports on a schedule, and asking the data a question in English when a chart does not exist yet.
For administrators, IT and compliance.
Who can do what, how identity is federated, where the data sits and how long it stays there.
The reference material published today. Everything linked here is live, we do not list a page we have not written yet.
Endpoint-by-endpoint reference for the public API, with request and response shapes for integrating IndeForms with your own systems.
Read the API docsConfiguration walkthroughs for the patterns people ask for most: permit to work, lockout tagout, shift handover, inspections and chain of custody.
Browse recipesHow the platform is configured in manufacturing, utilities, construction and the other sectors we work in, including the standards those records answer to.
See your industryWhat is in each subscription, what the platform meters, and how a cloud account differs from an on-premise or air-gapped install.
See pricingAsk the people who build it. Tell us what you are configuring and what it did instead, and we will give you a straight answer, including when the answer is that the product does not do it yet.
Export the form or tell us the form name and the submission reference. Most questions about a rule that did not fire, or a connector that did not deliver, are answered by looking at the actual definition and the run log.
Support never impersonates a user account. Everything we do on your behalf is a named, audited action against your account, so there is always a record of who did what.
If you run the platform in your own data centre or air-gapped, we work from the support bundle you generate. No inbound access to your network is required.