Use case diagram can't name my actor properly

Question

So I have a problem. I'm making a use-case diagram for an e-commerce store. But I've been told that one of my actors can't be named server as it's not outside of the system. Any Ideas on what this actor can be called instead? This actor is taking care of most admin functions. Below is a simple image of what it looks like.

Answer 1

You don't need an actor to represent the server. The server is part of your system, and in use case analysis you treat the system as a black-box.

You should simply delete the current Server actor.