These guides cover the administrative side of the dashboard: how your workspace is branded, who can sign in and what they can do, how customers are separated into organizations, and how API keys are minted for integrations.
Two admin levels appear throughout. An instance owner administers the whole workspace — every organization, instance settings, and instance-wide API keys. An organization admin administers one organization — its members, forms, and data. The RBAC concept page explains the full model.
The guides
- Instance settings — app name, logo, icon, brand colors, the support email and where it surfaces, email sending over SMTP, and media storage visibility. Instance owners only.
- User management — inviting people, the invitation email, the five organization roles and what each allows, per-form assignments, and removing a user from an organization.
- Organizations — creating organizations, what stays scoped inside one (members, forms, records, data sources, webhooks), deactivation, and when to run one organization versus many.
- API keys — minting keys in the dashboard: organization-scoped versus instance-scoped, scopes, rate limit overrides, the show-once plaintext rule, and revocation.
Who can do what
| Task | Requires |
|---|---|
| Edit instance settings | Instance owner |
| Create or deactivate organizations | Instance owner |
| Mint instance-scoped API keys | Instance owner |
| Invite users, manage roles | Org admin or user admin |
| Assign forms to users | Org admin, user admin, or form admin |
The organizations and instance settings pages appear only for instance owners. The other actions are enforced when you try them — the database refuses changes your roles do not allow. Ask an instance owner if you need a level you do not hold, or contact support if you are not sure who that is.
These guides cover administration only. For building forms, reviewing records, and connecting data sources and webhooks, see the product guides. For programmatic access to the same resources, see the Customer API.