Building Forms as a Team: How Role-Based Access Works in WandForm

Forms look like simple things from the outside. Behind the scenes — especially for teams — they’re organizational assets that need the same access control as any other business tool.

The four roles

Owner — full control, including billing, workspace settings, and the ability to delete the workspace. Each workspace has one owner (transferable).

Admin — all of Owner’s permissions except billing and workspace deletion. The right role for team leads and department heads.

Editor — can create, edit, publish, and archive forms; can review submissions; cannot manage team members or billing.

Viewer — read-only access to forms and submission context. Useful for stakeholders who need visibility without editing rights — policy reviewers, clients, executives.

Why this matters for agencies

If you’re an agency building forms for clients, you need clean separation between your work environments. WandForm’s multi-workspace model gives you a separate workspace per client. Editors work inside the client workspace. The client gets a Viewer seat so they can monitor their own data without touching the form configuration.

On plans that include branding controls, the client-facing form can reduce WandForm’s default public-form branding.

Enterprise identity planning

Large organizations often need identity-provider integration, automated provisioning, and stricter audit controls. Those identity features are planned roadmap work rather than part of the shipped production surface today.

Until then, workspace roles remain the primary access-control model.

A note on form-level permissions

The current RBAC model applies at the workspace level — everyone in the workspace sees all forms in that workspace. Form-level permissions, where specific forms are restricted to specific team members, remain roadmap work until they are implemented and documented.