US English (US)
FR French
DE German
PL Polish
SE Swedish
FI Finnish

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

English (US)
US English (US)
FR French
DE German
PL Polish
SE Swedish
FI Finnish
  • Log in
  • Home
  • Identity Governance and Administration (IGA)
  • IGA solution library
  • Processes and use cases
  • Use case library
  • User lifecycle management

Self-Service: Create New Users, Update User and Departing User Information

IGA use case for receiving personal- and employment information from Self-Service, contains also on-boarding and off-boarding use cases

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Service Management
    Matrix42 Professional Solution Matrix42 Core Solution Enterprise Service Management Matrix42 Intelligence
  • Identity Governance and Administration (IGA)
    IGA overview IGA solution library
  • Platform
    ESM ESS2 ESS Efecte Chat for Service Management Integrations Add-ons
  • Release Notes for M42 Professional, IGA, Conversational AI
    2026.1 2025.3 2025.2 2025.1 2024.2 2024.1 2023.4 2023.3 2023.2 2023.1 2022.4 2022.3 Release Information and Policies
  • Other Material
    Terms & Documentation Guidelines Accessibility Statements
  • Services
+ More
    • Service Management

    • Identity Governance and Administration (IGA)

    • Platform

    • Release Notes for M42 Professional, IGA, Conversational AI

    • Other Material

    • Services

Self-Service: Create New Users, Update User and Departing User Information

IGA use case for receiving personal- and employment information from Self-Service, contains also on-boarding and off-boarding use cases

Self-Service: Create New Users, Update User and Departing User Information

This use case describes scenarios where end-users can add new users (onboard), update existing users, and manage departing user information (offboard) through Efecte Self-Service.

It is important to separate these use cases from user lifecycle management use cases. Difference between these two is that Self-Service use cases are the starting point for user lifecycle management use cases. Self-Service is actually one of the options to how to receive users personal and employment information to IGA solution. This means that use cases described in this document will end to user lifecycle management use cases.

Terminology

Below you can find terminology for Self-service use case related to user creation, updates and departing users. Check terminology for user lifecycle management, and don't forget to also check Efecte Glossary.

Terminology Description
Create new user Means that user adds personal and employment related information to source system(s), IGA solution receives information and starts provisioning for user creation towards directory/directories. 

Create new users is also a service in Self-Service.
On-board new user On-boarding has wider scope than creating users, in IGA context it also contains request access rights service, and if scope is extended it can contain also physical/privilege access right requests or other services.

On-board new users is also a service in Self-Service.
Update existing user information Means that user makes personal and employment related changes to source system(s), IGA solution receives information and starts provisioning for user update towards the directory/directories. 

Update user information is also service in Self-Service.
Update departing user information Means that user adds employment end date to source system(s), IGA solution receives information and starts several different actions for the departing user, process ends when all related access rights, auditing responsibilities etc. are removed from the user. 

Update departing user uses same service with update user information in Self-Service.
Off-boarding Off-boarding can have wider scope than just disabling user accounts and removing access rights, like for example in cases where IGA solution is managing physical accesses, there might be a need to return keys or other equipment's.
 
 

Use Case Descriptions

Use Case for Create New User (Onboarding)

"Create new users" service in Self-Service can be an individual service, or it can be bundled up with request access right service and in that case, the service is usually called “on-board new user”. If the customer is using other relevant services in their Self-Service, those can be bundled up with IGA onboarding service.  

  Description
Overview In this use case is described how new user's personal and employment information is added to Self-Service. 
Operators
  • Self-Service
  • IGA solution
  • Manager/end-user (in the use case is referred to manager)
Prerequisites Customer has defined user lifecycle management use cases and settings for work period and account management. Customer has granted accesses to Self-Service for those users who can access either create new user or onboard user services.
Result New users personal and employment information is received to IGA solution and user lifecycle management processes can be started. 
New user creation process (on-boarding)
  1. Manager logs in to Self-Service.
    • Login options can be found from here. 
  2. Manager opens create new user or on-board user service.
  3. Manager selects if user already exists in IGA solution.
    • In case user has only one work period related to directory account, this selection is not valid.
    • In case user can have multiple work periods, this selection is needed because manager could want to create new work period for existing user or re-hire departed user. 
  4. If manager is creating entirely new user, manager adds required personal and employment information to the service (name, title, start date, manager name etc.).
  5. If manager is creating new work period for existing user, manager adds required employment information (no need to add personal information, user is selected from the list).
    • Customer can decide if all users are listed, or is only for example internal user listed there. 
  6. If onboarding service is used, manager will request access rights in the next phase, moves to confirmation after all services are fulfilled.
  7. If create new user service is used, manager will next move to the confirmation.
  8. Manager can return to previous step(s), until submitting the request.
  9. Request is sent to IGA solution and user lifecycle management processes are started.
  10. Manager can see status and added information for the request in Self-Service and they can comment the request.
  11. User can see requests made for them.
Reporting 

Reporting in Self-Service is depended on customer settings and access rights to the services, but end-users and managers can see for example:

  • My things (visible to all users) shows information related to the user, like for example active access rights and work periods.
  • My employee (visible to managers) shows information related to subordinates like for example active access rights and work periods.
  • My requests (visible to all users) shows information about requests made by the user or request, requested for the user.
  • Approvals (visible to users with approval responsibilities) shows information about all request what the user has approved / declined.
  • Requests for others (visible to managers) shows requests what the user has made to other users.
Ready-made services in Self-Service
  • Create new internal user.
  • On-board new internal user (bundled with request access right service).
  • Create new external user.
  • On-board new external user (bundled with request access right service).
 
 

Use Case for Update User Information

End-users and manager can update users personal and/or employment related information from Self-Service. 

  Description
Overview This use case describes how existing user's personal and employment information can be changed from Self-Service. 
Operators
  • Self-Service
  • IGA solution
  • Manager/end-user (in the use case is referred to manager)
Prerequisites Customer has defined user lifecycle management use cases and settings for work period and account management. Customer has granted accesses to Self-Service for those users who can access to update user information service.
Result Existing users personal and employment information changes are received to IGA solution and user lifecycle management processes can be started. 
Update user information
  1. Manager logins to Self-Service.
    • Login options can be found from here. 
  2. Manager opens update user information service.
  3. Manager selects subordinates work period from the list and day of change for the request.
  4. Manager can request change for users personal and/or employment information.
  5. If request is about personal information, manager fulfills requested information and it will be updated to users identity and all work periods & accounts.
    • Personal information: first name, last name, spoken name/preferred name, second name.
    • Depending on user lifecycle management processes, user will get new credentials, for example email address.
  6. If request is about change of employment information, manager fulfills requested information and it will be updated only to selected work period.
    • Employment information: employment start date, employment end date (if end date is added, process moves to departing user use case), manager name, title, cost center, organizational unit, user type, contract type.
    • If customer is using automated rules, user's access rights (entitlements) and/or business roles are updated/removed according to changes.
  7. Manager will move to confirmation after fulfilling all requested information and can submit the request
  8. Request is sent to IGA solution and user lifecycle management processes are started.
  9. Manager can see status and added information for the request in Self-Service and they can comment the request.
  10. User can see requests made for them.
Reporting 

Reporting in Self-Service is depended on customer settings and access rights to the services, but end-users and managers can see for example, 

  • My things (visible to all users) shows information related to the user, like for example active access rights and work periods.
  • My employee (visible to managers) shows information related to subordinates like for example active access rights and work periods.
  • My requests (visible to all users) shows information about requests made by the user or request, requested for them.
  • Approvals (visible to users with approval responsibilities) shows information about all request what the user has approved / declined.
  • Requests for others (visible to managers) shows requests what the user has made to other users.
Ready-made services in Self-Service Update user information
 
 

Use Case for Departing Users (Offboarding)

Use case for departing users, is using same service as update user information in Self-Service. Only difference is that when end date is added to the request, it will start departing user process.

  Description
Overview This use case describes how departing user process is started from Self-Service.
Operators
  • Self-Service
  • IGA solution
  • Manager/end-user (in the use case is referred to manager)
Prerequisites Customer has defined user lifecycle management use cases and settings for work period and account management. Customer has granted accesses to Self-Service for those users who can access to update user information service.
Result Existing users personal and employment information changes are received to IGA solution and user lifecycle management processes can be started. 
Update user information
  1. Manager logins to Self-Service .
    • Login options can be found from here. 
  2. Manager opens update user information service.
  3. Manager selects subordinates work period from the list and day of change for the request and end date for the work period.
    • If user has several work periods, all work periods needs to be ended before user is permanently departed.
  4. Manager will move to confirmation after fulfilling all requested information and can submit the request.
  5. Request is sent to IGA solution and user lifecycle management processes are started.
    • If customer is using automated rules, user's access rights (entitlements) and/or business roles are removed according to end date.
  6. Manager can see status and added information for the request in Self-Service and they can comment the request.
  7. User can see requests made for them.
Reporting 

Reporting in Self-Service is depended on customer settings and access rights to the services, but end-users and managers can see, for example: 

  • Manager can see status and added information for the request in front page in Self-Service and they can comment the request.
  • My things (visible to all users) shows information related to the user, like for example active access rights and work periods.
  • My employee (visible to managers) shows information related to subordinates like for example active access rights and work periods.
  • My requests (visible to all users) shows information about requests made by the user or request, requested for them.
  • Approvals (visible to users with approval responsibilities) shows information about all request what the user has approved/declined.
  • Requests for others (visible to managers) shows requests what the user has made to other users.
Ready-made services in Self-Service Update user information
 
 

Delivery Instructions

Configuration Instructions

Relations to other use cases:

  • User lifecycle management
  • Account management 

 

Preparation tasks, 

  1. User lifecycle management and work period management use cases need to be configured in IGA solution
  2. Generating and provisioning directory accounts, IGA account management need to be configured in IGA solution.

 

Configuration instructions: 

  1. Use (publish/unpublished) the appropriate forms as agreed in the definition work shops with the customer. The options are:
    • Onboard for internal users (bundle, including request access rights)
    • Onboard for external users (bundle, including request access rights)
    • Create new internal user (single service)
    • Create new external user (single service)
    • Update user information (single service) for both internal and external users, and this same service is used for departing users (offboarding). 
       
  2. If you are working with an environment where only one work period per user is used, remove the following attributes from the ESS form(s):
    • User exists?
    • User
    • New work period for existing user will be created. If you 
      wish to update existing work period, please use Update 
      Subordinate Information form
       
  3. Self-Service is using OU paths to find correct person datacards from IGA solution and granting access to the correct site where the forms are published.
    • Set the correct organizational units on the Sites tab.
       
  4. IGA related forms in Self-Service are displayed to users based on directory groups, ready-made roles can be found in the roles tab, for example IGA for managers. 
    • Change the groups used in the baseline to the actual customer directory groups defined in the delivery.
       
  5. Information added to Self-Service is now send as IGA service request to IGA solution.

 

 

 
 

System- and Approval-testing Instructions

When IGA solution is delivered, we recommend to use Efecte Delivery Management tool for test cases, test findings and test phase reporting. These instructions referring to ready-made test cases in the tool.

Testing users created/updated/departed from Self-Service:

  1. Login to Self-Service with one of the manager type of test users
    • Create new internal and external users.
    • Update existing subordinate information.
    • Update personal information (first name, last name etc.).
    • Update employment information (title, cost center, organizational unit).
    • Create new work period for existing user (not valid if user has one work period and one directory account).
    • Off-board existing subordinate .
    • Validate that Self-Service is showing request status correctly in the front page.
    • Validate that request history is showing information correctly in Self-Service.

Follow up user lifecycle management testing instructions for validating that data is received correctly and account management testing instruction for validating that data is provisioned correctly. 

 
 

 

personnel control user management iga self service create user update user

Was this article helpful?

Yes
No
Give feedback about this article

Table of Contents

Related Articles

  • Configuring "My Cases" View

Copyright 2026 – Matrix42 Professional.

Matrix42 homepage


Knowledge Base Software powered by Helpjuice

0
0
Expand