IndeForms help centre

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.

​

Browse by what you are doing

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.

Getting started

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.

  • Organisation setup: Organisation settings, branding, timezone and locale defaults.
  • Adding users: Invite admins, reviewers and field agents, and what a seat means.
  • Roles and access: Component-level read and write access, and who can publish a form.
  • Your first form: Build a short form, publish it, dispatch it to one agent, read the result.
  • Installing the mobile app: Android and iOS install, sign-in and first form download.

Building forms

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.

  • Pages, sections and questions: The form hierarchy and the column layouts a section can use.
  • Question types: Text, choice, date, camera, sketch, signature, barcode, geo, audio, calculation, aggregation and API questions.
  • Repeatable sections: Many rows inside one submission, with calculation and aggregation footers and min/max row limits.
  • Validation: Regex, length, range, decimal precision and currency on individual answers.
  • Rules: IF/THEN/ELSE logic that shows, hides, requires, locks, sets or clears a question, a page or a whole section.
  • Rule groups: Tag rules into named groups so a capture pass and a sign-off pass run different logic on the same form.
  • DREL prefill: Expression tokens that pull an earlier answer, a form value or a date into labels, defaults and outbound calls.
  • Sources and option lists: Static options, source-backed dropdowns, dependent lists and an Other free-text escape hatch.
  • Versions and publishing: Publish a version, see which version a submission was captured against, restore an older one as a draft.
  • Translations: Per-field translations, publish-time drift detection and the language selector agents see.
  • AI assistance: Describe a form in plain language, or photograph the paper original, and correct the draft it produces.

Dispatching work to the field

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.

  • Direct dispatch: Send to named agents; each one gets their own instance of the form.
  • Broadcast dispatch: Offer one job to a group; the first agent to accept claims it and the rest are released.
  • Pull forms: Let agents start a form themselves from a list of what they are allowed to run.
  • Scheduled dispatch: A cron schedule in your timezone, an Excel roster of recipients, and per-column default values.
  • Dispatch payloads: Pre-fill fields at dispatch time, and edit the payload before it goes out.
  • Teams and the calendar: Group agents for targeting and approval routing, and read the organisation-wide dispatch calendar.
  • Chasing a job: Unaccepted dispatches, due dates, force-pull of a stale form and dispatch decline handling.

Mobile app and offline capture

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.

  • Working offline: Forms, option sources and rules are already on the device; capture, validation and calculations all run locally.
  • Sync and queued submissions: What happens on reconnect, how a queued submission behaves and where an upload failure shows up.
  • Camera and video: Timestamp and GPS watermarking, the recording length cap and gallery rejection rules.
  • Barcode, GPS and sketch: Binding a submission to an asset by scan, capturing a location fix, drawing on a diagram.
  • OCR into a field: Photograph a plate or label and extract the value on device, optionally filtered by a regex.
  • Voice input and audio notes: Dictate into a text field, or record an audio note and transcribe it on device.
  • My submissions: An agent read-only view of what they have already sent in.
  • Device security: Data-at-rest encryption, PIN and biometric unlock, auto-lock and recovery when a device is wiped.

Approvals and workflows

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.

  • The workflow canvas: Trigger, condition, branch, merge, loop, timer, spawn-form, notify and invoke-API nodes.
  • Approval nodes: Group policies for all, any, quorum, majority, consensus and advisory decisions.
  • Choosing approvers: A named user, a group, the submitter manager, a value read from a form field, or the same person as an earlier node.
  • Escalation and reminders: Nudge a parked approval, escalate it upward, or let a timer decide.
  • E-signature: Password or signature-pad signing on approval and on submit, enforced on the server for both web and mobile.
  • Send for edit: Return a submission to its author with comments and a rework cap so it cannot loop forever.
  • Variables and conditions: Run-scoped variables, step references and conditions that read an earlier node output or another form latest submission.
  • The approvals inbox: Where approvers see what is waiting, on the web and in the mobile app.

Integrations and API

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.

  • Connectors: Email, FTP, S3, OneDrive, SharePoint, Box, Dropbox, Google Sheets, Salesforce, ServiceNow, SAP S/4HANA, Dynamics 365, Veeva Vault, TrackWise and MuleSoft.
  • Output formats: PDF, JSON, Word and ZIP bundle, and when each is generated.
  • Field bindings: Map form answers onto a target record for structured destinations instead of dumping a blob.
  • The API question type: Call your endpoint from inside a form, on load, on change, on a button or on submit, and write the response back into fields.
  • Authentication: Basic, bearer, API key, OAuth2 client credentials, OAuth2 password and custom schemes, all held encrypted server-side.
  • Testing a call: The builder dry-run, what it shows you, and how to read a failed call.
  • Egress control: The per-customer allowlist, the private-range block, and why an outbound call may be refused.
  • Call logs: The redacted API call log, what is stored, and how long it is kept.

Analytics and reporting

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.

  • The operations dashboard: Overview, dispatch, agents, reviews, data quality, and geo and time tabs, with shared date and form filters.
  • Drilling down: From a form or an agent row into the submissions behind the number.
  • Exports: XLSX and CSV, detailed per-question exports, and queued exports for large date ranges.
  • Scheduled reports: Generate on a cron and mail the result to a recipient list.
  • Analytics chat: Ask a question in English, see the SQL it produced, get a chart back, and save the query.
  • Custom dashboards: Drag widgets onto your own layout, including saved queries and geo maps.
  • Data quality and anomalies: Field completion rates, photo and GPS coverage, and statistical outlier review on submitted values.

Administration and security

For administrators, IT and compliance.

Who can do what, how identity is federated, where the data sits and how long it stays there.

  • Users and roles: Create roles, grant component-level read and write access, and audit who has what.
  • Single sign-on: SAML 2.0 and OIDC federation, per-customer discovery by email domain, and mapping IdP groups onto roles.
  • Data isolation: Why every customer gets its own database, and what that means for your data.
  • Retention and erasure: Retention policies, and running a subject access or erasure request as an auditable job.
  • Quotas and usage: Seats, submissions, storage and API calls, the warning threshold and what gets blocked at the cap.
  • Encryption: Encrypted connector and API credentials, and mobile data-at-rest encryption per customer.
  • On-premise operations: Licensing, the heartbeat, signed update bundles for air-gapped sites, and support bundles.

Documentation that is already written

The reference material published today. Everything linked here is live, we do not list a page we have not written yet.

API reference

Endpoint-by-endpoint reference for the public API, with request and response shapes for integrating IndeForms with your own systems.

Read the API docs

Workflow recipes

Configuration walkthroughs for the patterns people ask for most: permit to work, lockout tagout, shift handover, inspections and chain of custody.

Browse recipes

Industry guides

How the platform is configured in manufacturing, utilities, construction and the other sectors we work in, including the standards those records answer to.

See your industry

Plans and metering

What is in each subscription, what the platform meters, and how a cloud account differs from an on-premise or air-gapped install.

See pricing

Still need help?

Ask 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.

Send us the form, not a description of it

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.

We will not log in as you

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.

On-premise installs are supported the same way

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.