Termination Workflow

218cam
Tera Contributor

I am curious if what I am thinking is possible.  Imagine this scenario.  An employee is hired.  Their manager puts in an Access Request for their Active Directory account.  A week later puts in an Access Request for Adobe Product.  A month later, puts in an Access Request for Docusign then another Access Request for a Zoom account.  A year passes by and that employee gets fired.  

I would like for the manager (or anyone really) to submit a termination request.  That request should (hopefully) pull down any and all prior requests and spin off "removal tasks" to the respective teams responsible for each application (One task to Adobe team, one to Docusign team and one to Zoom team and one to AD team).  I am sure there is some table somewhere that stores info from Access Requests somehow.  This type of flow was instituted at a former employer of mine but I was not "tight" with the SNOW team.  At my new employer, we have SNOW but since we do not have a SNOW team onsite, we tend to shy away from using it very heavily, relying on this procedure above being completely manual.  If the above is possible (Im sure it is), how possible is it without very much coding.  Current employer is not fond of having alot of coding done in SNOW because coder employees might not be available to troubleshoot if things break.  It would be easier if the whole thing was GUI so that anyone with an IT brain can troubleshoot it.  Believe me that I want nothing more that to put this together because it is poor me who does the manual portion (I just started at this place with automation aspirations).  FYI, whatever ideas you guys can share, ill be doing in my personal instance of SNOW prior to presenting to my boss.  I am not a SNOW guru and I dont have that power in my corp instance but am an IT pro with over 20 years experience working in different systems.  I'm just putting that out there in case it helps with how you guys give the tips.  

0 REPLIES 0