These pages explain how FieldScroll works beneath the dashboard and the mobile app. They are written for the people who ask "how does it really work" — the buyer comparing platforms, the IT reviewer checking isolation guarantees, the integrator deciding where data lives.
Each page stands alone. Read the one that answers your question, or read them in order for the full picture.
The five concepts
- Data model — the entities that make up a workspace: organizations, users, forms, published versions, and records, and how they relate. Start here if terms like "draft" and "published version" are new.
- Multi-tenancy — how organizations keep your customers separate inside one workspace. Covers what is shared across organizations, what is isolated, and where that isolation is enforced.
- Roles and permissions — who can do what. Instance owners, the five organization roles, and how permissions gate database access and API keys.
- Security — an honest overview of the security posture: encryption in transit and at rest, database-level row isolation, API key handling, and the audit trail on every record.
- Offline and sync — what happens when a field crew loses signal. How forms are cached on the device, how drafts survive restarts, and why submissions never produce merge conflicts.
How these pages relate to the rest of the docs
The concept pages describe mechanisms; the product and admin pages describe the screens and workflows built on those mechanisms.
- For day-to-day usage — building forms, reviewing records, generating reports — see the product docs.
- For workspace administration — inviting users, managing organizations, minting API keys — see the admin docs.
- For integration work — authentication, pagination, webhooks — see the API docs.
- For a vocabulary reference, the glossary defines each term in one or two sentences.
If a claim on these pages matters to your evaluation — an isolation boundary, an encryption property, a sync guarantee — and you want more detail than the page gives, contact support. We would rather answer the specific question than have you assume.