Team ownership

Important forms should not depend on one person’s private account or memory.

WandForm is designed for team-owned form workflows. That means the team should know who can edit the draft, who can publish, who reviews submissions, and who handles failed follow-up.

Assign ownership before publishing

Before a form goes live, decide:

• which workspace owns the form
• who can edit the draft
• who can publish changes
• who reviews submissions
• who handles delivery recovery
• where exports or audit evidence are stored when needed

These decisions prevent a public form from becoming an orphaned process.

Keep one canonical public link

Use one public link for each live workflow. If you replace an old form, update old pages, emails, help articles, and internal docs.

Multiple active links for the same workflow can split responses and make reporting unreliable.

Review access over time

Update access when:

• someone leaves the team
• a client or project changes owner
• a form becomes more sensitive
• a workflow moves from test to production
• a new team takes over follow-up

Team ownership is not only an admin setting. It is part of operating the form responsibly.

Make responsibility visible

A team-operated form should make these questions easy to answer:

• Is this form live?
• Which version is live?
• Who owns the workflow?
• Are submissions arriving?
• Did supported follow-up work?
• What failed?
• What can we safely change next?

If the team cannot answer those questions, improve the workflow before adding more forms.