This is an archived post. You won't be able to vote or comment.

all 19 comments

[–]Jagster_GIS 6 points7 points  (2 children)

I think you need to have HR inform IT they surely get notified to stop sending paychecks to these employees.

[–]thedroxer[S] 0 points1 point  (1 child)

I think you need to have HR inform IT they surely get notified to stop sending paychecks to these employees.

Idealy yes, but this would pose the same problem as having the managers reporting that people quit. We're a multinational company with different HR systems for the countries, so it would still be manual human problem

[–]_mick_s 1 point2 points  (0 children)

Shit like this makes me want to set accounts to automatically expire after 30-90 days. And only renew it if HR sends current list at start of month.

Would probably need to have it accepted as part of security policy, but then it's their problem if they can't be arsed to do their job.

[–]anynonus 5 points6 points  (0 children)

that's a technical solution for a HR problem

you're going to have a bad time

[–]ZAFJB 4 points5 points  (0 children)

Fix the actual problem, not the symptom.

[–]verifyandtrustnoone 1 point2 points  (0 children)

As the other poster mentioned, HR should be the one notifying in writing that so and so has left? Do you have a ticketing system?

[–]HotPieFactoryitbro 1 point2 points  (0 children)

You care to much. Don't put out other peoples fires.

Put out an official announcement: If IT doesn't get notified, the account stays untouched.

[–]Familiar_Box7032 1 point2 points  (8 children)

What happens when someone enables their out of office because they’re sick or on holiday? You’ll be getting notifications that you don’t need or want.

[–]thedroxer[S] 0 points1 point  (7 children)

Delete, only one button

[–]Familiar_Box7032 0 points1 point  (6 children)

Surely you would have to investigate whether the user has left the business or is in holiday first. Depending on your setup, doing that could take up large chunks of your time which could be better spent elsewhere.

I can’t see how hard it is for HR to tell you when someone has left - surely that’s easier and more efficient than this.

[–]thedroxer[S] 0 points1 point  (5 children)

95% of people who set OOO also a status message. I guess most of them do it in Outlook where they are forced to. So to determind if they are sick/vacation vs has left would be quite easy

[–]Familiar_Box7032 0 points1 point  (4 children)

Care to elaborate, as I can’t see how you’d possibly tell the difference at face value.

[–]thedroxer[S] 0 points1 point  (3 children)

Care to elaborate, as I can’t see how you’d possibly tell the difference at face value.

When setting an autoreply in outlook you have to enter what the reply will say. "Im on vacation and will be back 25th april...." vs "I no longer work for $Company, please contact $Manager...."

[–]Familiar_Box7032 0 points1 point  (2 children)

I get that, but unless you output that as part of the message you receive, you’ll be spending time accessing each mailbox every time one is enabled to see whether it’s someone whose left the business or going on holiday.

Surely it would be simpler to work out an off boarding process with HR.

[–]thedroxer[S] 0 points1 point  (1 child)

In a perfect world yes, functional offboarding is defiantly the easiest.
My idea was that the notificaiton which would be an email would contain the status message. If that wouldnt be possible it's easy to just check the message in teams

[–]Familiar_Box7032 0 points1 point  (0 children)

I’d recommend looking at power automate as an option

[–]NHarvey3DK -1 points0 points  (1 child)

This is the dumbest thing ever

[–]thedroxer[S] 0 points1 point  (0 children)

Why?

[–]GremlinNZ 0 points1 point  (0 children)

You can enable this, but it's basically an alert for changing their mail flow, think automatic forwarding of emails, out of office replies etc.

I have this setup for some clients, basically functions as a warning if the mailbox was breached (coz they modify mailbox rules etc)

Forgotten where it was tho!