This article outlines on how to handle a User Creation request from the users.
| Info | ||
|---|---|---|
| ||
PI1 and SI1 systems requests should be handled in the PQ1_001 systemIDM. PI1 and SI1 systems are sensitive systems as mainly the finances are handled through this system. Solvay uses Central User Administration (CUA) configuration which helps manage all the user master records in the PI1 and SI1 client systems centrally from the PQ1_001 system. |
Identifying the Tickets :
When the users asks for a creation of the user in the ticket in PI1 or SI1 system, then it can be identified as a User Creation. Alternatively, when the user does not exist in the system and the access has to be given to the user, then it is considered as a User Creation. These tickets may have the accompanying information like the Name of the User / ID, Reference User Name / ID, Systems, etc. Below is an example of how the ticket may look like.
| Info | ||
|---|---|---|
| ||
It is always a good idea to check if the Reference User and the User exist in the system. If the Reference User is invalid, ask the User / L0 team User for a new Reference User. If the User already exists in the system then there will be no need to create again. Hence, this would save time. |
...
Providing the Access :
Before proceeding with these kind of tickets, we need to always check the approvals. The approvals for the PF1 and SF1 system are managed by the L0 Teams depending on the region. If there are approvals are missing in the ticket then the ticket has to be transferred to the respective L0 Team (Bangkok, Lisbon or Curitiba) asking them to get the approvals. Also, we need to ask for a Reference User ID for the new user creations or the list of the roles which have to be added.
The request is approved if an agent from the L0 Team mentions that the it is approved or if the one requesting the access is the User's Manager. Examples can be seen below :
Important : There are few special cases for approvals in the PI1 and SI1 systems. The approval process is different for the different types of requests : CICC Online Roles, Z3F-ADH* roles and BCM Roles. For more details on this, please go through the below confluence article and once you have done come back to this article to continue the User Creation process :
PI1 and SI1 Requests - Approval Process
Providing the Access :
...
...
...
...
- When we have the required approvals, we need to check if the user to be given the access exists in the IDM.
- After that please provide the access using IDM . (Note - Roles are getting added as Privilege , also if you are providing PI1 access by default you have to add SI1 too)
- Finally, inform the user regarding the User creation d and Resolve the ticket.
2. BCM / CICC Online Access :
Case 1 : If we get the request from anyone of the below contacts, we can go ahead and create the user with the basic role in PI1 system and with the Z3F-BCM* roles (if requested) and Resolve the ticket.
Etienne Lobet (CICC - Z3F-ADH* roles)
Etienne Lobet (CICC - Z3F-ADH* roles)
Etienne Lobet (BCM - Z3F-BCM* roles)
Etienne Lobets (BCM - Z3F-BCM* roles)
Signed Users :
We get this request from the Etienne Lobet to create users under this category. For any users under this type, we create users the user with the required/mentioned roles and another with naming convention XXXXX_S and assign the role : Z3F-BCM-SIGN-SB and user group : ZZZ :SIGN. For this type users we provide the password to users, once user changes the password of the signed user (XXXXX_S) to productive we change the user type from dialog to service since to avoid the password expiry.
Note - We have to contact Veerle to create user XXXXX_S when not found in IDM
Case 2 : If we do not get the request from anyone in the above contacts, we will inform the user to contact the above any contacts to get the access to BCM / CICC Online access, and then Resolve the ticket straight away.
We have now finished the request for the User Creation of a new user in the PI1 and SI1 system.
...
...
Related articles
| Content by Label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page properties | |||
|---|---|---|---|
| |||
|