Closed garethrees closed 1 year ago
It should be made clear what this "closed" status means. (Prevention of login, and alert mails, though not a prevention of transactional emails / notifications relating to a users' own requests?)
Perhaps notifications relating to a users' own requests should also be prevented?
A user who can't login to classify a response shouldn't be asked to do so. (Comment arises from support mail on WhatDoTheyKnow from a user in this position)
A user who can't login to classify a response shouldn't be asked to do so. (Comment arises from support mail on WhatDoTheyKnow from a user in this position)
I've raised #5090 for this as we've had another WDTK user complain about being asked to do just that this weekend.
It should be made clear what this "closed" status means.
Yes. We already have a "Danger Zone" on a admin user edit page, so we can make it more like the GitHub approach:
We'll want to be able to unfold details for each dangerous action:
I think this was done by https://github.com/mysociety/alaveteli/pull/4869
I think this was done by https://github.com/mysociety/alaveteli/pull/4869
That was Close and Anonymise. This issue is just for a "Close" button (closing does different things to adding ban_text
).
Closing in favour of https://github.com/mysociety/alaveteli/issues/7646.
We now have
User#closed_at
that prevents users signing in.We should have a button that allows admins to permanently close a user account.
Required by https://github.com/mysociety/alaveteli/issues/3148.