T
TxGoat
Guest
wow.. so many inboxes
you poor guy Tx having to put up with all that
Think of it this way, 100+ people sharing an inbox, one message gets sent to that inbox, that's 99 unnecessary email transmissions on the network, all because one admin doesn't want to take ownership.
I had a similar situation at one of my clients. I went with an old-school, extremely effective solution. I created an account on the domain and called it scheduling or rooms or whatever. I gave it an extremely complex password that was like 27 letters so it's practically hack proof. I created calendars under that account and shared them with everyone. Voila. If I need to change someone's permissions on a calendar, I can easily do that. If they need another calendar for some other use, it's easy to do. Everyone can see the schedules for the rooms and you can easily audit who is making changes to them as well.
That may work but what I'd prefer is to have 1 person as the admin so that if there are scheduling conflicts they can decide who gets the room for the allocated time and who has to reschedule. As much as I'd like to employ a "first come first served" policy, considering our parking lot policy is "execs up front even if they come in at 10:00am and leave at 3:00pm" I'm sure if they have a schedule in place their schedule supersedes some lower level supervisor that's already scheduled a team meeting.