Joiner Processes:

1. When user enter into a company HR will update user details in HRMS in Active Status-Once
User data get sync into HRMS To IDM User get created into IDMonce user created under
managermanage will place a request on behalf the user

a. If user raise a request it will go for the manager approvals

b. If user line manager raise a request it will goes for the next level of the approvels.Here
Manager level skip
c. Once manager approves the user request it will go for the application owner approvals.
2. Once all approvals are completed it will go for the provisioning
3. Here we will be done two types of provisioning
a. Manual provisioning
b. Automated Provisioning

a. Manual provisioning: once all approvals are completed then the request hit to the Administrator for
Manual Provisioning.

In Manual Provisioning admin log in his target system or native system and he will manually create the
login id and password and sent the credentials to the user via email.

User will retrieve the credentials from email and he will login to the target system.

B.Automated Provisioning: (Admin will verify the user information and he will complete the request.)or
(Application is already integrated with idm)

then the request hit the target system and the account will get created and the credentials will sent via
email to the user automatically .Here application already integrated to the IDM.

User raise a request Ticket number generated Manager ApprovalsApplication owner approvals
Adminprovisioning.

Mover Processes:

Incase user is moving to different department then the mover request will be generated. If user wants
to change the access (read to write abccess to databases) he will raise the amended request.

Her user who are already having access to the target system and want to amend/Modify the access they
will raise Amend Request. As a administrator we will modify access as per the request

Once all approvals are completed then it will go for the provisioning

1. Manual Provisioning: Admin will login on the target system and he will update user access from
user level to super admin access level.
 2. Here admin only changes the user access level and he not creates any password. Because user
already created in database and password creation is not required.

Example:
Role profile: In_Pune_Financial_application

1. My Eclipse --- > Disable request

2. Database - Read access -- Amendment Request (required read and Write access)
3. Java -- > Disable Request
4. Arc sight -- Read Access -- Disable Request
5. Headset -- > No Change
6. Outlook - > No change
7. Chat room -- > No change
8. Transportation (Cab) --> Change
9. Mysql --> New Request

If user doesn’t required access -- Disable required raise

User required access to new application --> new request raise
User access should be changed --- Amendment request raised
User access should not be change -- > No change

Amendment request will be raise by the user ---> Ticket no generated--> Manager Approval-->
Application owner approval--> Administrator ---> provisioning.

Leaver Access:

When user leaves the company HR Will updates the user Status to inactive and User profile will get sync
to IDM with inactive status.

De provisioning request will triggered automatically for all the applications

Once all approvals are completed we will go for provisioning

Manual provisioning: Admin will login on the target system and he will directly remove the access to the
user.

Automated provisioning: user will be removed on the particular target system.