There's really no point. File servers are stateless by design. A person cannot be "present" on a server. It's not like a phone call, where someone can call up and be on the line. Stateless servers are only connected when performing a transaction. They connect, transfer whatever needs to be transferred, and disconnect... boom-boom-boom.
The only time the server is active is when it's responding to a request. Therefore, what's the point of giving you a notification? Why would you need a notification? You couldn't take any action on anything, because whatever was done happened instantaneously.
Receiving a notification after-the-fact only serves to inform you that something has happened. That's what logs are for. Logs keep a record of previous activity. This is more suited for purpose.
Instant notifications serve to provide time-critical messages, hence the "instant" delivery. Usually this is to signal prompt action from the user. Server actions would have to wait in a "pending" state while the user deals with the notification. Since file servers are stateless, there is no "pending" state for the server action to "wait" in while the user responds to the notification. This stateless design renders instant notifications useless.
Either read the server logs, or get some sort of log management utility. Getting instant notification on server activity will NOT happen unless you find some way to monitor the server logs in real time, which is ridiculously inefficient.
You're kinda out of options.