If you're building a site for a client there are a few scenarios:
You are hired to build the thing. In this scenario you complete the build, transfer all access and everything to them and train them on how to use it.
You are hired to operate the thing (This might include #1). The client doesn't want to worry about this thing breaking, so they keep you around to make sure it works. In this model you will likely create different roles. A super admin for you and maybe someone else, and other more granular roles that allow the others to do their work without too much risk of messing up
You are hired to operate but someone else is the admin. A very common scenario is you get brought in to fix or enhance, but you aren't able to do anything you want. In this model you have to work with the people who have full access to either take action on your behalf, or slowly trust you with elevated access.
Most of the time, operating sites is where you find out if you really made something easy to use. If you ask around most developers hate maintaining and operating for a really simple reason: It's not that easy.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you're building a site for a client there are a few scenarios:
Most of the time, operating sites is where you find out if you really made something easy to use. If you ask around most developers hate maintaining and operating for a really simple reason: It's not that easy.