IT & Engineering · Onboarding & handoffs

Joiner, Mover, Leaver IT Automation

Starts when: A start, a role change or a termination becomes effective

Free plan · Outcome verification included · You approve every connection

How it runs

Six stages, from the moment it starts to the checks that keep running afterwards.

  1. It starts

    A start, a role change or a termination becomes effective

  2. Awish plans it and asks for each app

    The apps it needs are connected one at a time, with your permission, before anything runs.

  3. It does the work

    Exactly as the request below describes, across the connected apps.

  4. It stops where a person should decide

    Treat the HR system as the source of truth and require extra approval for privileged access.

  5. It verifies the outcome

    After each run, Awish checks that the ticket, alert or access change was applied and recorded.

  6. It keeps monitoring

    Failures, silent failures and connection health are watched on every plan; anomalies, root cause and recommendations on Business.

The request it runs

This is what opens in chat when you use the template. Change any part of it before anything connects.

“I need an automation that takes care of the joiner, mover and leaver IT process. Trigger it when an employee start, role change or termination becomes effective. It should create, modify or revoke the accounts and groups according to the role, create the device ticket, notify the manager, schedule the timed revocation and log every change. Connect it with Workday, Okta and Jira Service Management. Treat the HR system as the source of truth and require extra approval for privileged access.”
Apps it connects
  • Workday
  • Okta
  • Jira Service Management

Monitoring included

What Awish watches once this template is running.

  • Outcome verificationEvery plan
  • Silent-failure detectionEvery plan
  • Connection healthEvery plan
  • Hours saved and ROIEvery plan
  • Anomaly detectionOn Business
  • Root-cause explanationOn Business
  • Recovery recommendationOn Business

How monitoring works

Questions about this template

Can I change where it stops for approval?

Yes. Open the template in chat and say where you want it to stop. The plan updates before anything connects.

What if one of these apps is not connected yet?

Awish asks you to connect each app it needs, one at a time, before the workflow runs. You can decline any of them.

How does Awish know this workflow worked?

After each run it checks that the ticket, alert or access change was applied and recorded, in the app where that should happen. If a run reports success but the result is missing, it flags a silent failure.

Run it on your own apps

It opens in chat with the request written. See the plan, approve each connection, and Awish verifies the outcome from the first run.

Free plan · No credit card required