You should know how in IT things just aren't designed to be that easy most of the time. If it wasn't designed to originally do it probably wont do it.
Bullshit.
That needs to be auto-added when I rely to you!
Anyone who knows software knows how to change a field in a database to change the status of a post, an account or whatever. It's not a mystery.
I've made systems work that I had zero experience operating by tracing from the application to the objects they access and the entities they read and key off of. Changing that field changes the status of the attribute, hence the specific row in an object.
My whole career was as a designer, tester, configuration manager, problem solver, programmer, database designer and administrator, and systems engineer.
I'm "anyone who knows software." You're wrong.
If the account was unlocked before, the associated status fields can be changed BACK to make it unlocked again. If there's no GUI for this, and it's a valid use case, then the system was poorly designed, but that doesn't mean it can't be updated at the DBM level.