1 reply
by timwalsh
I'm probably going to get into some internal politics here, but is this the case?
In my mind, there are only a couple of reasons to limit access times:
1. A user, or group of users, has proven untrustworthy (Internet abuse, spying/prying, equipment abuse, etc.)
2. You have some process running after hours that will not complete successfully with logged-on users.
3. You have a bandwidth-intensive process running after hours that will be interfered with by logged-on users.
4. You work in a super-secure environment where limited access is mandated.
It sounds like you already have a policy and/or process in place whereby users can have extended access with supervisor approval. If it isn't written down, it may be time to formalize it.
The bottom line here is this:
Assuming you can't change management's mind about limiting access hours (which is probably the case or you wouldn't be asking this question), one of two things needs to happen.
1. If it is a matter of a user asking for extended access and needing supervisor approval, it should be incumbent on the user to ensure you get the request with the necessary approval.
2. If it is a matter of a supervisor requiring a user to work hours requiring extended access,it should be incumbent on the supervisor to ensure you get the request.
You should not take the heat for someone else's miscommunication. To "help out," you might want to create a simple "Extended Access Hours Request" form. On the form (preferably in bold letters), state that unless you get this form, correctly (and completely) filled out, and in a timely manner, extended access cannot be granted.
This form will fulfill two purposes:
1. It puts both users and management on notice that you shouldn't be held responsible for something you didn't know about; and
2. It provides a paper trail for you should there be any finger pointing as to whether you were told o
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending