Summary
Follow-up to #584 (account suspension / Right to Restriction), implemented in #607.
The suspend/unsuspend feature currently toggles User.is_active but does not record an audit trail of when the restriction was applied or lifted, or by whom. Issue #584 notes this is desirable but defers it, because a separate audit-log mechanism is still in flight.
Once the audit-log feature is merged, wire the suspension actions into it.
What to do
- In
ConsoleSuspendUserView and ConsoleUnsuspendUserView (home/views/console.py), record an audit event when a user is suspended/unsuspended, capturing:
- the subject user
- the staff member who performed the action (
request.user)
- the timestamp
- the action type (restriction applied / lifted)
- Optionally surface this history in the console user detail page.
References
Summary
Follow-up to #584 (account suspension / Right to Restriction), implemented in #607.
The suspend/unsuspend feature currently toggles
User.is_activebut does not record an audit trail of when the restriction was applied or lifted, or by whom. Issue #584 notes this is desirable but defers it, because a separate audit-log mechanism is still in flight.Once the audit-log feature is merged, wire the suspension actions into it.
What to do
ConsoleSuspendUserViewandConsoleUnsuspendUserView(home/views/console.py), record an audit event when a user is suspended/unsuspended, capturing:request.user)References