This article outlines on how to handle a User Creation request from the users.

PF1 is the Production Environment SF1 is the Pre Production Environment and QF1 is the Quality Environment.

Identifying the Tickets :

When the users asks for a creation of the user in the ticket in PF1 or SF1 or QF1 systems, 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.



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. If the User already exists in the system then there will be no need to create again. Hence, this would save time.

Approvals :

Before proceeding with these kind of tickets, we need to always check the approvals. The approvals for the PF1 system are managed by our team itself. If there are approvals are missing in the ticket then we need to ask user to provide approval of manager. 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.

If the request is approved by manager in ticket or if the one requesting the access is the User's Manager. An example can be seen below :


Providing the Access :

If a user asks to add the role (or in case of a User Creation) in the PF1 system then the same roles has to added in the SF1 and QF1 system's too. But the vice-versa should not be done, i.e. if the user needs access in the SF1 or QF1 system's then the same has to provided only in the SF1 or QF1 system. Also, only the roles with a Direct Assignment are to be added to the user.





We have now finished the request for the User Creation of a new user in the PF1, SF1 and QF1 system's.