Termination Process
The termination process is triggered when HR terminates the employee account and access in HRMS. IDM reconciles the data from HRMS and disables the user account's profile in IDM and all the corresponding target systems.
Use Case
Terminate User - Day 0
Use Case | Terminate User - Day 0 |
---|---|
Brief Description | Terminate user process is initiated when HR terminates the user accounts and its accesses in HRMS. IDM reconciles the records from HRMS and detects the termination and disables the user account's profile in IDM and corresponding target system. |
Actors |
|
Trigger Events |
|
Preconditions |
|
Post-Conditions | Success
Fail
|
Basic Flow |
The basic flow for the termination process is explained in the below activity diagram: On the day of termination
|
Terminate User - Day 10
Use Case | Terminate User - Day 10 |
---|---|
Brief Description | Terminate user process is initiated when HR terminates the user accounts and its accesses in HRMS. IDM reconciles the records from HRMS and detects the termination and disables the user account's profile in IDM and corresponding target system. |
Actors |
|
Trigger Events |
|
Preconditions |
|
Post-Conditions | Success
Fail
|
Basic Flow | After 10 days of termination
|
Terminate User - Day 30
Use Case | Terminate User - Day 30 |
---|---|
Brief Description | Terminate user process is initiated when HR terminates the user accounts and its accesses in HRMS. IDM reconciles the records from HRMS and detects the termination and disables the user account's profile in IDM and corresponding target system |
Actors |
|
Trigger Events |
|
Preconditions |
|
Post-Conditions | Success
Fail
|
Basic Flow | After 30 days of termination
|
Terminate User - Day 90
Use Case | Terminate User - Day 90 |
---|---|
Brief Description | Terminate user process is initiated when HR terminates the user accounts and its accesses in HRMS. IDM reconciles the records from HRMS and detects the termination and disables the user account's profile in IDM and corresponding target system. IDM disables the user profile and sets the de-provisioning date as 95 days after the current date |
Actors |
|
Trigger Events |
|
Preconditions |
|
Post-Conditions | Success
Fail
|
Basic Flow | After 95 days of termination
|
Diagram
The diagram below illustrates the basic flow to terminate the user process.
Topics | Questions | Response |
---|---|---|
Brief description | A brief description only focuses on the de-provisioning date. IDM disables the user profile and sets the de-provisioning date as 95 days after the current date | |
Post Conditions-
| There is another scenario which should be considered as failure- Failed to disable accounts which are in a provisioned state | |
Post Conditions-
| Need an email template detail for each notification. The template should have the following detail- Mail Subject, Mail Body, Mail Signature, Sender DL/email, and Recipient DL/email | |
Basic Flow- After 10 days of termination- | Is there a separate requirement for 10-day revocation and 10-day disable? | |
Basic Flow | Do we have separate requirements for 0-day revocation,10-day revocation,30-day revocation, and 95-day revocation of Entitlement or accounts? As per the current state of system Entitlements, Accounts or Roles there is no field/metadata which holds information like 0-Day revocation,10-day revocation,30-day revocation, or 95 days revocation. | |
There should be a separate requirement for employee status change from A/L/P to S (suspended). Is there any specific requirement for different status changes other than the one mentioned above? | ||
After 30 days of termination- | Need clarity on who will create tickets to revoke all disconnected accounts and assign them to whom. |