When user account is locked there is no information about this fact in admin panel. Team menu only shows if account is suspended. Another thing is that admin is not able to directly unlock account because there is no unlock option and resetting password from admin panel does not unlock that account. It is only possible to unlock account if you suspend it and then unsuspend.
Solution:
Hey @PaszaVonPomiot!
Sorry for late response.
One thing i've spotted is that if i am logged in as a none admin user and i change my status in the database to locked and refresh the admin panel, the admin spins forever. (403 response from server, which is correct). I assume that will also happen if i simply suspend the user in the admin panel with my blog owner (with 2 different browsers). I expect a redirect to the sign in page. cc @kevinansfield
When user account is locked there is no information about this fact in admin panel
Yeah that is correct and that i think has to be fixed, that is confusing. As blog owner, you won't see any status update in the UI.
add unlock button for admin/owner
The user can unlock himself by resetting the password. A user is only "locked" if he was imported. No need to add an unlock button. If the locked out user tries to login he will see
Your account is locked. Please reset your password to log in again by clicking the "Forgotten password?" link!
To confirm there are 2 actions points here:
I've change the owner to a locked account and now I'm stuck. Can you heklp me with that?

@pollusb not sure if there's an easier way but changing the value of 'status' column in DB from 'locked' to 'active' might help (I assume that if you're here looking for help you're self-hosted).
Think I found the solution:
mysql -u root --password=PASSWORD bitnami_ghost -e "update users set status = 'active'"
@pollusb this seems to be the way to go.
That is not a solution for production software.
Locked accounts are intended to be unlocked via password reset. There's some suggestion that there's a bug but no reproduction case here that we can use to track it down.
unlocking via 'forgot password' resulted in a spinning wheel followed by Request was rejected due to server error.
transforming @pollusb 's solution for sqlite worked great.
sqlite3 --header /path/to/database/connection/filename.db 'update users set status="active" where slug="myslug"'
the "server error" wasn't listed in the server (ghost - i didn't check nginx logs) logs but the client showed: GET https://ghost.example.com/ghost/api/v3/admin/users/me/?include=roles 403 (Forbidden)
@keithpjolley please open a new issue following the issue template if you believe there's a bug in the forgotten password flow.
Thanks!
Most helpful comment
Think I found the solution:
mysql -u root --password=PASSWORD bitnami_ghost -e "update users set status = 'active'"