Short answers first, links for depth. If your question isn't here, check common errors or contact support.
Mobile app
Does the mobile app work offline?
Yes. Published forms download to the device when you sign in, so you can open and fill them with no connection. Submissions made offline queue in on-device storage and upload on their own once the phone is back on a connection — either right after you submit, or the next time you open the app. The sync icon shows an amber dot while anything is still waiting.
Why don't I see a form on my phone?
Two usual causes, in order of likelihood:
- The form isn't published, or isn't assigned to you. Building a form doesn't make it visible — someone with builder access has to publish it and assign your user to collect with it. See the quickstart for the build-publish-capture flow.
- The device hasn't synced since publishing. Tap the sync icon in the header, or sign out and back in — both trigger a sync.
If neither helps, confirm with your administrator that your user belongs to the organization the form was published to.
What happens to my drafts if I lose signal?
Nothing is lost. Drafts stay in on-device storage until you submit them; submitting is what queues a record for upload. Keep the app installed until your work has synced — uninstalling the app removes on-device storage, including unsynced drafts.
I submitted a record on my phone. Why isn't it in the dashboard?
The device was probably offline (or on a weak connection) at submit time, so the record is queued locally. On the Records screen it shows an upload-pending cloud icon, and the sync icon in the header carries an amber dot. Reconnect and reopen the app and the upload starts on its own; you can also tap the sync icon to try immediately. If the record still doesn't arrive, sign out and back in to force a full sync.
Forms and records
Can I edit a form after publishing it?
Yes. Publishing creates a versioned snapshot — devices use the published version, and any edits you make afterward stay in the draft, invisible to field users, until you publish again. You can keep iterating without disrupting collection in the field.
What happens to existing records when I publish a new version?
Nothing happens to the records themselves — they are never rewritten. Before the publish goes through, the dashboard tells you what your change means for them: a compatible change (adding a field, editing labels, changing list choices) lets existing records appear together with new ones under the new version; a breaking change (changing a field's type or how it is answered) keeps earlier records on their own versions, visibly marked. The full story is in form versions.
Where do submitted records go?
Open Records in the dashboard. Each submission shows its captured data, photos, and device metadata. Search and filters narrow the list as volume grows.
Workspace and sign-in
How do I add a user?
A workspace administrator invites them from the dashboard. The invitation email contains a link where the new user sets a password. Until they accept, they can't sign in to the dashboard or the mobile app.
I forgot my password. How do I reset it?
Use Forgot password on the dashboard sign-in page, or Forgot your password? on the mobile app's sign-in screen. Either one sends a reset email to the address on your user record. On a phone, type your email first, then tap the link — it opens in the phone's browser, where you set the new password and then return to the app to sign in. The same credentials work in both places.
Workspaces that sign in through their own identity provider do not show this link on the phone, because there is no FieldScroll password to reset — those accounts recover through that provider.
Where do I set the support email for my workspace?
Workspace owners configure it in instance settings. Once set, it appears on the Support screen in the mobile app and in the footer of every email the platform sends.
API and webhooks
Where do I find my API key?
Mint keys in the dashboard at /api-keys. The full token is shown once, at creation — store it in your secret manager. If you lose it, mint a new key and revoke the old one. Details, scopes, and rotation steps are in authentication.
Why didn't my API call fire a webhook?
By design. Mutations made through the Customer API do not fire webhook events — you already know the change happened, because you made it, and firing would create loop risk. Dashboard and mobile mutations fire webhooks normally. The full reasoning is in webhooks and the API.
My API request failed. What should I include when reporting it?
The request_id from the response (also in the X-Request-Id header). It lets us join HTTP logs, audit rows, and observability events for that exact request. See contact support for the full checklist.