Notify When an Okta User Is Activated, Profile Updated, and Deactivated, a 3-Part Joiner/Mover/Leaver Video Series

Okta Workflows is a no-code platform for automating identity processes. 

This blog post is based on a question asked during office hours or the #okta-workflows channel in MacAdmins Slack: How to create a joiner/mover/leaver flow? 

Getting started

Joiner, Mover and Leaver is a common scenario at many companies.

At a high level:

• Joiner – when an employee joins the company. For example, grant access to applications, subscriptions, and add to various groups
• Mover – when an employee moves within a company. For example, change group memberships, change role/title, and other permissions
• Leaver – when an employee leaves a company. For example, move files ownership to a manager, and cancel app access and subscriptions

Okta Workflows

The three videos will show you how to start building such automation.

1. Notify when an Okta user is activated

Watch the video

In this video you will learn how to build a flow to notify when an Okta user is activated. The flow has the following steps:

• ⚡user activated ➡️ notify in Slack, send an email, save to a table

2. Notify when an Okta user profile is updated

Watch the video

In this video you will learn how to build a flow to notify when an Okta user is activated. The flow has the following steps:

• ⚡user profile updated ➡️ notify in Slack

3. Notify when an Okta user is deactivated

Watch the video

In this video you will learn how to build a flow to notify when an Okta user is deactivated. The flow has the following steps:

• ⚡user deactivated ➡️ call API

Get your Workflows questions answered

Do you have a question about Okta Workflows? Not sure how to build a flow? Join the weekly community office hours to get help.