Skip to content

Registration Workflow Modes

Not sure whether signups should create accounts right away, wait for an admin, or stay in review-only? These workflow modes let you match GriffinForms registration to how your site actually runs.

Overview

GriffinForms adds a dedicated Accounts setup surface inside the form builder so a registration form can do more than collect entries. You can configure how account creation should happen, which email field should drive it, how duplicate-account conflicts should behave, and whether the workflow should run immediately or wait for admin follow-up.

Each setup is attached to one email field. A single form can have one registration setup or multiple setups, depending on how many user-account workflows the form needs to drive.

Onboarding Starter

If you use the GriffinForms onboarding flow, you can now start with a dedicated User Registration goal instead of building the whole registration form from scratch.

  • The starter always includes an email field and a safe default Accounts setup.
  • You can optionally add first name, last name, username, and password during onboarding.
  • If you include a password field, the starter wires it into the registration setup automatically.
  • You can still open the builder later and refine role assignment, CAPTCHA, confirmation email behavior, and other workflow settings.

This is a fast way to launch a signup form without losing access to the full Accounts configuration later.

Creation Modes

  • Immediate Create — GriffinForms creates the account after the normal post-submission pipeline is allowed to run.
  • Pending Admin Activation — the submission records a pending target and waits for an admin to activate account creation from the submission page.
  • Manual Review Only — the workflow records the target but does not create the account until an admin deliberately chooses to do so.
Recommended default: use Immediate Create when the form is already trusted and the account should be created automatically. Use pending/manual modes when staff review is part of the process.

Duplicate-Account Behavior

  • Show Error — block the frontend submission before save when the email already belongs to an existing WordPress user.
  • Update User — keep the submission and update the existing user with supported mapped data.
  • Accept Form / Do Nothing — keep the submission without changing the existing user.

These choices matter because they define whether a registration form behaves like a hard signup gate, a profile update workflow, or a softer intake process.

Quick Start

  1. Open the form builder and launch the Accounts modal.
  2. Select the email field that should drive account creation.
  3. Choose the creation mode and role.
  4. Choose the password strategy and optional profile mappings.
  5. Choose the duplicate-account behavior.
  6. Save the setup, review builder warnings, submit one test entry, and confirm any imported message references still make sense on this site before publishing.

Next steps

If you are deciding how strict your signup flow should be, next read Password strategies and Profile mappings. If something still feels off after testing, share the form goal and a sample entry in WordPress.org support and we will help you troubleshoot.