Seat Types & Licensing
42Forms uses a hierarchical seat-type model. Each tier includes all capabilities of the tiers below it.
Seat Hierarchy
Section titled “Seat Hierarchy”| Tier | Level | Capabilities |
|---|---|---|
| view | 0 | Read-only access to submissions and dashboards |
| act | 1 | Create and edit submissions, submit for review |
| build | 2 | Create projects, design forms, configure sync |
| admin | 3 | Full access - manage org, members, connections, licenses |
Assigning Licenses
Section titled “Assigning Licenses”Licenses are assigned via SQL in Snowsight:
CALL FORTY_TWO_FORMS_APP.CORE.SET_LICENSE('USERNAME', 'admin');The API polls the license_commands staging table every 30 seconds and applies changes automatically.
How Seat Types Interact with Permissions
Section titled “How Seat Types Interact with Permissions”Seat types are global (per-org) and gate access to features. Partition-level permissions (can_read, can_edit, etc.) provide granular control within those features.
For example, an act-tier user can create submissions, but only in partitions where they have can_submit permission. A view-tier user cannot create submissions regardless of partition permissions.
Default Behavior
Section titled “Default Behavior”- Users are auto-provisioned on first login via the Snowflake gateway
- New users default to
viewtier until an admin assigns a license - Personal organizations are created automatically for each user