Approve user accounts
Available since Exponential 6.0.15 (in development, not in a release yet).
Summary
The workflow event "Approve user accounts" (doc/eng-us/bc/6.0/user-account-approval.md), modelled on the approval event (ezapprove): on content/publish before, a user account whose version places it in a group that requires approval waits until an approver accepts it.
Description
The workflow event "Approve user accounts" (doc/eng-us/bc/6.0/user-account-approval.md), modelled on the approval event (ezapprove): on content/publish before, a user account whose version places it in a group that requires approval waits until an approver accepts it. The approval event can only ask for a section; this one asks where the account is placed, which is what decides the rights its user gets.
The approval is the approval event's: an item of the collaboration handler "ezapprove" in the approvers' and the author's collaboration lists, accepted or denied there; the item and the process are linked in ezapprove_items. On top, the approvers get a mail with the link to the item (no key: they sign in), and the request and the decision are recorded in the audit log (access.user.approval.request, .approve, .deny). After the decision the workflow continues at once (expUserApproval::deci
Type
| Type string | Class file |
|---|---|
| expuserapprove | kernel/classes/workflowtypes/event/expuserapprove/expuserapprovetype.php |
See also
Help: bc/6.0/user-account-approval.md
Generated example: expuserapprove
Added to the reference for Exponential 6.0.15: the 4.x reference had no page for this event type.
Contributors
- Graham Brookins Updated
Comments
Add a comment