Employee Off-boarding

If there’s the Employee Onboarding module I’m wondering where’s the Employee Offboarding one? Onboarding is fixing only half of the process, doesn’t it?

Please consider adding the Employee Offboarding module to Freshservice.

Thanks,

Jiri

I agree, but take it 1 step further please.

In the Onboarding it is wonderful the amount of detail we can break it down to, for each user role.  There is no process for the Employee Maintenance.  We often have users changing roles within the organization.  This requires everything that was loaded in the Onboarding for one role, have to be viewed, and the Employee then gets moved into another role, so it is a comparison of what do they have, and what do they need.  In some cases it is adding to the existing permissions/software.  But in some it could be removing.  You have all of the pieces to track this in the solution, but they are not tied together.  It also then flows into the Offboarding as well.  

@Denise.S.P Excellent suggestion. I fully concur with your thoughts, and think this would be a great addition to the processes.  I know it would make my SD team happy 

Having needed to reclaim thousands of IT assets from leavers or their colleagues due to ineffective leavers procedures in a large company, this would be a great addition. 

I have just started to Build a WF using orchestration in freshservice for off boarding process. 
I have never built this sort of thing before. But so far I have a WF that is designed to disabled the user account in Local AD and revoke access in azure and disable account in Azure. 

So far it is working O yeah and it scans 6 different domains to find the user ;-) 

@Chef040_1 That sounds awesome!  The more you can automate, the better!  I would love to see your workflow design, we do not have our system linked but it would bring a good cost / time awareness that perhaps would get us to be able to one day.

@Denise.S.P Yep we have automated quite a lot so far.
We’re an hybrid set up so we had to wait for the Powershell option to be enabled before we could get working on the leaver process. But once that was enabled we can now move user to a non sync OU to stop the sync to Azure from Local AD. 

Hook up all the systems you can ;-) we so for have Azure and Powershell and Teams linked to FS. 

@Chef040_1 This sounds very cool - do you have some of the steps written out?  How hard was it to make the Orchestration work with O365 or Azure AD?  What about other 3rd party SAAS software?

THanks!

Thanks Denise, same for us. Being able to define at least 3 types: Onboarding, Maintenance and Offboarding would be great.

Bundle Service-Products are only a bad workaround, you can add various service requests, but not tickets (only tasks if needed). But some actions required you want a as a ticket and not as a public visible SR (e.g. tweaking access rights according the new role) 

Same here. We use Freshservice for multiple departments (IT, HR, Payroll etc.) and so using Bundled Service Tickets and workflows are a bad workaround. Need an Offboarding module

This really need to be looked at by Freshservice, and many companies are going through ISO and other audit, and they always ask about the offboarding process. 

I would like to also suggest when an offboarding process is started it should automatically attach offboarded users' software / licenses and assets to the ticket so we can easily identify and remove accesses.