Blog Sections Open

Using WebLoginPE with Administrator-Approved Registration

Not every registration should create an instantly active user. Some projects need a moderated approval step in the middle.

Instant registration is convenient, but some sites need more control. The old WebLoginPE question here was about a workflow where users register first and an administrator confirms the account later.

Why Teams Want This

  • closed communities need manual vetting
  • business portals need account approval before access is granted
  • spam reduction matters more than immediate sign-in

What This Changes

Registration becomes a two-step workflow: collect the user data safely, keep the account inactive or limited, then add an explicit approval action for admins.

The main lesson is that user management is a workflow question as much as a form question. The registration form is only the beginning.

Newer post

Running Multiple FormIt Forms on One Page Without Cross-Talk

A practical note on FormIt when several forms share one page and start interfering with each other during validation or submission.

Older post

Making `paramEditFull` Work with `shk_widget` in Shopkeeper

How to reason about paramEditFull, TV-backed parameters, and shk_widget output when Shopkeeper parameter editing stops behaving correctly.