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 view analytics; cannot manage team members or billing.

Viewer — read-only access to forms and analytics. Useful for stakeholders who need visibility without editing rights — compliance teams, 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.

White-labeling means the client sees their brand throughout — custom branding, their logo, their colors. WandForm is invisible.

Enterprise identity roadmap

Large organizations often need identity-provider integration, automated provisioning, and stricter audit controls. Those enterprise 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 (restricting specific forms to specific team members) are on the roadmap for Q3 2026.

If this is a blocker for your use case, contact us — we can discuss an Enterprise arrangement that meets your needs sooner.