> ## Documentation Index
> Fetch the complete documentation index at: https://hc.saas-manager.biz.nuro.jp/llms.txt
> Use this file to discover all available pages before exploring further.
# 3-2. Configure a Workflow for Employee Offboarding
> Learn how to set up a workflow that automatically deprovisions SaaS accounts when an employee leaves, and sends notifications via Slack or email.
**Permission for this service:** This feature requires **Admin** or **Automation Manager** permission.
**SaaS status:** The target SaaS must already be connected. The connection must use administrator privileges (including API permissions) that allow account creation and deletion.
This guide explains how to configure a workflow that automatically deprovisions SaaS accounts when an employee leaves. The workflow also sends notifications via Slack or email.
#### Configuration flow
After completing the [prerequisites](/en/it-management/workflows/90k8f1lee0-workflows), configure the workflow in three main steps.
1. [**Pre-configure automation (mapping)**](/en/it-management/workflows/ms4wo45v27-admina-automation-wic): Set up the mapping with the connected services.
2. [**Create and publish the workflow**](#offboarding-steps): Define the workflow conditions and activate it.
3. **Notifications**: Verify that notifications arrive via the selected method ([Slack](#slack-notifications) or Email).
Steps to configure employee offboarding
1. Go to Automation > \[Create automation] > click "Employee offboarding."
2. On the "deprovision" builder screen, click "1. A terminated employee was removed."
3. Set the automation trigger condition (contract end date) and execution schedule.
Example: Target the work end date of February 1, 2026, and run indefinitely. To execute one day after the work end date (employment type: full-time employee):
Set contract end date: > After, 2026/02/01 | Employment type: Full-time | Execution schedule: > After, 1, day.
| Item | Description |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Contract end date** | Select \[Any date / Custom date] and choose a date from the calendar. A custom date excludes the specified date itself. The dropdown options are "Within / \< Before / > After." "Within" specifies a date range. |
| **\[+ Add another condition]** | You can add conditions for employee type / employee status / department. You can also add conditions for job title / work location / manager ID. You can also add conditions for company name / alternative email / display name / first name / last name. You can also add conditions for email address / employee number / notes / number of services / number of devices. You can also add conditions for [`custom fields`](/en/it-management/workflows/rdeflerejh-automation-custom). |
| **Execution schedule** | Select \[1 (number)] \[day/week] \[> After / On (date)] from the dropdowns. This is relative to the contract end date. |
4. Click "Parallel execution" to add the services to include in the workflow.
Select enabled services from \[+ Add another service].
5. Select the service displayed under "Deprovisioning (deprovision)."
To add multiple services to the workflow, turn on "Multiple selection."
The services listed under "Deprovisioning" are those you configured during [pre-setup (mapping)](/en/it-management/workflows/ms4wo45v27-admina-automation-wic).
6. Click the service you selected on the "Parallel execution" screen to display the "Settings" panel on the right.
Select the workspace name from the "Service settings - Workspace name" dropdown.
To configure multiple services, use \[+ Add another service].
7. Click "Notifications."
1. Click \[+ Add another notification].
2. On the "Message" screen, select the notification method: "Slack / Email."
To configure multiple notifications, turn on "Multiple selection."
For Slack setup steps, see [Slack notification setup](#slack) below.
3. Click the message you selected on the "Notifications" screen to display the "Settings" panel on the right.
8. Once all checks in the builder turn green, click \[Publish] or \[Dry Run].
9. On the "Confirm workflow automation settings" screen, enter a name for the automation and click \[Publish].
Note: You cannot use a name that is already registered.
10. When "Workflow has been published" appears, click \[OK].
Steps to set up Slack notifications
1. On the screen at step ⑤-(C) of the [new employee onboarding setup](/en/it-management/workflows/ygzni03g1c-admina-automation-wic-ggx#new-employee-onboarding-steps), the "Connect notification bot" screen appears. Click \[Connect bot].
2. The "Requesting permission to access your Slack workspace" screen appears. Review the details and click \[Allow].
3. The "Notification channel" screen appears. Click \[+ Add channel].
4. On the "Select a Slack channel" screen, specify the destination and click \[Select].
5. Confirm the "Notification channel" screen and click \[Save].
#### Notification content
When setup is complete, the workflow runs on the specified date and sends notifications. For details on when workflows execute, see [**Workflow execution timing**](/en/it-management/workflows/n2msl3q9um-admina-automation).
Slack notifications
* **First-time connection notification:** A channel-add notification is sent to the specified Slack channel.
* **Execution result notification:** On the scheduled date, a notification is sent to the specified Slack channel.
For the full setup flow, see [Getting started with Automations](/en/it-management/workflows/90k8f1lee0-workflows).