-
-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add button to close user account #4910
Comments
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) |
I've raised #5090 for this as we've had another WDTK user complain about being asked to do just that this weekend. |
I think this was done by #4869 |
That was Close and Anonymise. This issue is just for a "Close" button (closing does different things to adding |
Closing in favour of #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 #3148.
The text was updated successfully, but these errors were encountered: