Organizations are the isolation boundary in a FieldScroll workspace. Each customer of yours runs inside one: its users, forms, and records stay separate from every other organization's. The Organizations page in the dashboard lists all of them with member counts, org admins, and status — only instance owners see this page.
Creating an organization
Choose New organization and fill in three fields:
| Field | Notes |
|---|---|
| Name | The display name |
| Slug | Optional — generated from the name if left blank |
| Initial org admin email | Must be an existing user; they are granted the org admin role |
The org admin you name becomes the organization's first administrator and can invite the rest of its members. See user management for what org admins can do from there.
What lives inside an organization
| Resource | Scoping |
|---|---|
| Members and roles | A person's membership and roles apply to one organization at a time |
| Published forms | Forms are published to an organization; its members fill them out |
| Records | Submissions stay with the organization that owns the form |
| Data sources | Lookup data is owned per organization |
| Webhooks | Subscriptions deliver one organization's records |
| API keys | Organization-scoped keys can only address their bound organization |
Nothing crosses the boundary. A member of two organizations switches between them; they never see a blended view. The multi-tenancy concept page covers how this isolation is enforced.
Entering an organization as an instance owner
The organization switcher in the dashboard topbar lists every organization in the workspace when you are an instance owner, not only the ones you were added to. Switching into one puts you inside it — its forms, its records, its data sources — which is how you support a customer without asking them to add you as a member.
Two things to know. Entering an organization you are not a member of is recorded in the audit log; switching between organizations you belong to is not. And switching does not make you a member, so the organization's member list and its org admin count are unchanged by your visit. See roles and permissions for how this fits the wider permission model.
One organization or many
Run one organization per customer. That is the unit of isolation — each customer's users and data stay walled off, and you can hand its org admin role to someone on the customer's side. A single organization is fine when you serve one team or run everything yourself. The data model is the same either way, so starting with one and adding more later costs nothing. Splitting a single customer across several organizations is rarely worth it, since their users and records would no longer share a view.
Deactivating an organization
An organization's edit page has a deactivate action, available to the instance owner. Deactivation ends access for every member right away and signs out anyone whose only organization it was. The organization shows as Inactive; its records, forms, and media are kept — nothing is deleted. The instance owner can reactivate it from the same page, and members get access back on their next sign-in. Sessions that were ended at deactivation are not restored — people sign in again.
The customer API does the same thing. A DELETE on an organization
deactivates it and signs out the same members, so the API and the
dashboard button leave the workspace in the same state. See the
API reference.