Module deactivation 

Deactivation as an offboarding step (issue #173, step 4): an administrator deactivates a leaver and, in the same step, chooses what happens to what they still hold (see services::offboarding::holdings):

• hand their work over to a successor (ownership::hand_over_in: owned items, draft and rejected change orders, open change requests assigned to them, pending reviews) – and their manager role: the successor becomes a manager of every group the leaver managed;
• revoke (delete) their API tokens, so activating the account again does not bring old tokens back;
• release their check-outs (checkouts::release_held).

Deactivation, hand-over and token revocation run in one transaction; the check-outs are released afterwards, one transaction per revision, like every bulk release. Deactivating the only active manager of a group without a successor is refused unless the administrator confirms that the group is left without one.

Structs

DeactivationReport

What the deactivation did.

Offboarding

What to do besides deactivating the account.

Functions

deactivate

Deactivates a user as an offboarding step.

sole_manager_codes

Codes of the groups in which user is the only active manager (for the offboarding form; administrators only).