Definitions for the vocabulary used across these docs. Terms are ordered by how often you will meet them.
Workspace — your FieldScroll deployment: a branded mobile app, a web dashboard, and the data inside them. Workspace-level branding and settings apply to everything in it.
Organization — a tenant inside your workspace, usually one of your customers or business units. Users, published forms, and records are scoped to organizations.
Form — a structure for data capture, built in the dashboard form builder. A form in the builder is a draft; field users never see drafts.
Published form — a versioned snapshot of a form, released within its organization. Field users assigned to collect with it download it on sync; editing the draft does not change what the field sees until you publish again.
Version — the number a publish assigns: version 1, version 2, and so on. Every record remembers the version it was captured against. When versions are compatible, their records read together as one dataset; see form versions.
Breaking change — a form edit that changes what an existing field means or how it is answered, such as changing its data type. Records captured before a breaking change stay on their own versions instead of appearing under the new one.
Field — a single question or input in a form: text, number, date, choice, photo, signature, location, and more. Fields carry labels, hints, and validation rules.
Page — a section of a form, grouped behind a bar of buttons so a long form reads as a few short screens instead of one scroll. Pages change how a form is laid out, not the data it collects — the record stays flat. See forms.
Record — one submission of a published form: the captured values plus metadata such as submitter, time, and device.
Draft — a record in progress on a device, saved locally before submission. Drafts survive app restarts and missing connectivity.
Sync — the exchange between a device and the platform: published forms come down, queued records go up. Sync runs automatically on sign-in, right after a record is submitted, and when the app is opened with records still waiting to upload. It can also be run on demand from the sync icon, which shows an amber dot while anything is waiting.
Dispatch — checking a submitted record out to one field user. The record syncs to their device with its media for offline editing, and it is locked for everyone else until they resubmit it or the dispatch is revoked.
Data source — a reusable table of reference data (price lists, equipment registries, site lists) that lookup fields query, instead of hard-coding options into a choice field.
Report template — an HTML layout, designed in the dashboard, that the platform fills with a record's data and delivers as a PDF or HTML document. Each report sends its document to one or more destinations: email, a webhook endpoint you run, or a folder in Box or Google Drive.
Webhook — an HTTP notification the platform sends to your endpoint when something happens, such as a record being submitted.
API key — a credential for the REST API, minted in the dashboard. Keys are scoped, rate-limited, and revocable.