Approve registrations
A pending registration is an account whose registration is not finished. It cannot sign in until it is.
What you'll have at the end
Every waiting registration approved, rejected or reminded.
See what waits
./console exp:user:pending
./console exp:user:pending --search=example.org --limit=100The State column says what each registration waits for:
| State | Waits for |
|---|---|
email | the person to confirm the e-mail address (the account has an activation key) |
administrator | an administrator to activate the account |
workflow | an approver to accept the approval item of the account's publish |
The list is the newest first. exp:user:pending is the same as exp:user:list --state=pending.
Approve or reject one
./console exp:user:approve member1
./console exp:user:approve member1 --apply
./console exp:user:approve spam-account --reject --applyApproving activates the account as Users > Unactivated users does: the registration finishes, the account is
published and the welcome mail is sent. For workflow, the approval item is accepted and its workflow continues at
once.
--reject denies the approval item and removes the account for good, as the reject link of the registration mail
does. An account that is already active is never removed by --reject.
The audit records access.registration.approve or access.registration.reject.
Send the activation mail again
./console exp:user:resend-activation member1
./console exp:user:resend-activation member1 --applyThe command sends the activation mail again, with a new activation key, to an account that never activated. The old link stops working. Use it when the first mail was lost or its link expired.
To activate the account without the person, use exp:user:approve instead.
Related pages
- Approve a backlog of registrations: many at once.
- Approval of new accounts: how an installation holds new accounts back.
- Approving new editor accounts: the same in the administration.