mCAPS User ID & Access Management

Reference Document
Document Details:

User ID & Access Management Reference Document – Finnone CAPS &

Document Name
mCAPS
Document Owner Risk Management – Process Team

Page 1 of 9
Index:

Sl. No. Content Page no

A AD-ID Management for Outsourced staff 3
1. ID creation & Password generation 3
2. Password Reset 4
3. Forgot Password 4
4. ID Unlock 5
5. ID Deletion 6
6. ID Enable 6
7. ID Extension 7
8. Change in reporting authority 7

B Access to AD-ID based applications 8

1. Finnone Access 7
2. M-CAPS Access 8

C Entitlement Review 9

Page 2 of 9
This document covers the below processes:-
A. AD-ID Management for Outsourced staff
B. Access to Finnone CAPS & mCAPS
C. Entitlement Review

A. AD-ID management for Outsourced staff:

AD-ID Management covers:-

1. ID Creation, Password generation & ARMS mapping

2. Password Reset
3. Forgot Password
4. ID Unlock
5. ID Deletion
6. ID Enablement
7. ID Extension
8. Change in Reporting Authority

1. ID creation, Password generation & ARMS mapping:

Steps No. Activities FPR
Request 1 Reporting Authority (RA) shall shortlist the candidate, raise a request in RA
initiation in VSMS (Vendor Staff Management System) and upload the below
VSMS and documents, to initiate the process
documents
 Photo
upload
 KYC
 Previous employment details &
 User entry pass request form.
Request raised in VSMS shall flow to BU-SPOC for approval.
VSMS link

Encl: - VSMS User Manual (Annexure 1)

User Entry pass request form (Annexure 1.1)
Pre-hire 2 Post BU-SPOC approval in VSMS, HCM shall initiate Pre-hire background HCM/
Background verification through its RCU team. This background verification is HCM
verification applicable only in case of candidates who will be based at YBL premise RCU/RA
(on-site)
The HCM RCU team shall conduct verification and upload the report in
VSMS
RA shall access VSMS to check RCU status and act basis the findings.
Positive findings :
If the status is found to be positive, RA shall inform the candidate to join.

Adverse findings :
In case of adverse findings in pre-hire verification, exception approval
from Business Head i.e. President and above is mandatory to be submitted
to HR before the candidate joins. In case, candidate is not to be hired due

Page 3 of 9
 to adverse finding in pre-hire verification, same to be informed to HCM for
records.

AD-ID & E- 3 Once the candidate joins, RA shall update the joining date in VSMS for AD- RA / VSMS
mail ID ID and E-mail id creation. Team
creation
Once AD-ID and E-mail is created by VSMS team, RA shall get a
confirmation mail with AD-ID and E-mail details.
User shall get the ID and Password details through system generated text
message on his registered mobile
Note: - If the user is unable to use the password, User shall send a request
to RA/CSS for resetting of password
AD-ID 4 RA shall raise a request over mail to LAM team for mapping AD ID in RA/ LAM
mapping in ARMS (Access Roles Management System) team
ARMS
Mail shall be marked to dlapplamteam@yesbank.in
LAM team shall do the AD-ID mapping in ARMS and send a confirmation
mail to RA
In case, the RA wants to raise request for multiple no. of people, he can seek details from the vendor in the below
format for convenience of updation in VSMS, along with requisite documents as stated above.
Encl:- ID creation format (Annexure 2)

2. Password Reset: This is applicable in case the password gets expired

Steps No. Activities FPR
Password 1 For employees deployed at YBL premises: User/RA
reset
User shall reset the password on his own through switch user option. The
password reset can also be done by RA.
Note: - Password once reset is valid for 60 days only.
2 For employees deployed at vendor premises: Agency
FPR/
Agency FPR shall send a request mail, along with the existing User ID &
RA/Process
Password, to the Process team / RA for resetting the password.
Team
1. YES IT ticket needs to be raised for resetting the password and Mail can
be marked to - Helpdesk Corporate team at >>
helpdesk.Corporate@yesbank.in
2. RA/Process team shall reset the password from his own system
(Desktop) through switch user option and communicate to the user over
phone
Note:- Password expiry notification does not pop up in mobile based
applications. Hence the user needs to keep the track of password expiry
period.

Page 4 of 9
3. Forgot Password: This is applicable when user forgets password

Steps No. Activities FPR

Forgot 1 For employees deployed at YBL premises: RA/ User/
password Helpdesk
RA shall raise an E-ticket in ESM portal and send an e-mail along with e-
team
ticket number to helpdesk team for generating new password.
Mail shall be marked at helpdesk.Corporate@yesbank.
Helpdesk team shall generate the new password and share it with
requestor.
Note: - In One E-ticket, we can raise request for maximum three AD-IDs
2 For employees deployed at vendor premises: Agency
FPR/ RA/
Agency FPR shall send a request mail to the FPR of Process team / RA for
Process
generating new password.
team/
RA/ Process Team shall raise E-ticket in ESM portal and send an e-mail to Helpdesk
helpdesk team along with E-ticket number for generating new password. team
Mail shall be marked at - helpdesk.Corporate@yesbank.in
Helpdesk team shall generate the new password and share it with
requestor.
Note: - In One E-ticket, we can raise request for maximum three AD-IDs

4. ID Unlock: This is applicable if the ID gets locked

Steps No. Activities FPR
ID unlock 1 For employees deployed at YBL premises: RA
RA shall raise an E-ticket in ESM portal and send an e-mail along with e-
ticket number to helpdesk team for unlocking of AD-ID.
Mail shall be marked at helpdesk.Corporate@yesbank. Or call on
+914449159100
Helpdesk team shall unlock the AD-ID, confirm to requestor over mail and
close the e-ticket.
2 For employees deployed at vendor premises: Agency
FPR
Agency FPR shall share the AD-ID of employees over mail to respective
Collection Partner (Emp) / FPR of Process team for unlocking the AD-ID.

Page 5 of 9
 3 CP/ Process team shall raise an E-ticket in ESM portal and send an e-mail CP/
to helpdesk team along with E-ticket number for unlocking AD-ID. Process
Team
Mail shall be marked at DLhelpdeskchennai@yesbank.in or
DLhelpdeskifc@yesbank.in
Helpdesk team shall unlock the AD-ID, confirm to requestor over mail and
close the e-ticket.

5. ID Deletion:

Steps No. Activities FPR

ID/ Access 1 For employees deployed at YBL premises: RA/
deletion Agency
On cessation of service by user, RA shall raise the below requests in system:
FPR
 ARMS request for deletion for application access
 VSMS ID deletion request
LAM Team shall delete the application access as per ARMS request and
VSMS team shall delete the AD-ID in VSMS

For employees deployed at vendor premises:

Agency FPR shall share the exit details of user to RA/ Process team over
mail in the attached format.
RA/ Process team shall raise the below requests for deletion of AD-ID
 ARMS request for deletion for application access
 VSMS ID deletion request
LAM Team shall delete the application access as per ARMS request and
VSMS team shall delete the AD-ID in VSMS
Note:- Once the user resigns, RA can also update the date of resignation
and last working date in VSMS for auto deletion of VSMS ID on last
working day. ID deletion request should be completed within 7 working
days of user resigning.
Encl:-
1. ID deletion request form (Annexure 3)
2. ID deletion guidelines (Annexure 4)

Page 6 of 9
6. ID Enablement

Steps No. Activities FPR

ID Enable 1 RA shall raise a request in ARMS for enabling the ID as per guidelines RA/ LAM
attached. On submission of request, CID request no. is generated. team

RA shall forward the CID request no. to LAM team at

dlapplamteam@yesbank.in over mail.
LAM team shall enable AD-ID, send a confirmation mail to requestor and
close the request.
Encl:- ID enabling guidelines (Annexure 5)
Note :- If the AD-ID is not used for a continuous period of 60 days, ID gets
automatically disabled. This can happen in scenarios like user is on long
leave etc.

7. ID Extension:

Steps No. Activities FPR

ID Extension 1 AD-ID (for outsourced staff) needs extension every 6 months. User and RA RA/ LAM
shall get a system generated notification mail about ID getting expired. team
On receipt of notification mail, RA shall raise a request in ARMS for AD-
ID extension as per guidelines attached. On submission of request, CID
request no. gets generated.
RA shall forward the CID request no. to LAM team at
dlapplamteam@yesbank.in over mail.
LAM team shall extend AD-ID and send a confirmation mail to requestor
and close the request.
Encl:- ID extension guidelines (Annexure 6)

8. Change in reporting authority:

Steps No. Activities FPR

Raising 1 For change in reporting authority of any outsourced employee, RA shall RA/ LAM
request in raise a request in ARMS as per guidelines attached. On submission of Team
ARMS request, CID request no. shall get generated.
RA shall forward the CID request no. to LAM team
dlapplamteam@yesbank.in over mail.
LAM team shall change the mapping in ARMS and send a confirmation
mail to requestor and close the request.
Encl:- RA mapping change guidelines (Annexure 7)

Page 7 of 9
B. Access to Finnone CAPS & mCAPS application

 For Outsourced staff based out at YBL, either user or the RA shall raise the request in ARMS for access
 For on-roll employees, the employee himself shall raise the request for access

 For Outsourced staff based out at Vendor’s premise, the below process shall be followed

1. Finnone access:
Below steps shall be followed for giving finnone access to Outsourced staff based out at Vendor’s premise:-

Steps No. Activities FPR

Request to 1 RA shall send a request over mail to FPR of Process team for giving RA
create Finnone Finnone access to the user. RA shall ensure that AD-ID, role name and role
access description (in Finnone) shall be properly mentioned on mail as per job
responsibility of user.
Note: - RA shall provide the approval from SVP & above, if user also
requires access to reports in Finnone
Encl:-
1. Role Matrix -Finnone (Annexure 8)
2. ID creation format (Annexure 2)
3. Finnone User Guideline (Annexure 9)
ARMS request 2 Process team shall raise a request in ARMS. Process
A system generated mail is forwarded to RA and role approver (Process Team
Team)
RA & Role approver shall approve the ARMS request in system. RA /
Process
Team
Post approval, system request shall automatically flow to LAM team. LAM team
LAM Team shall create Finnone access, map the requested roles to user and
close the request in ARMS
A system generated mail flows to requestor and RA. Request status can be RA/User
viewed from the link provided in mail.
RA shall inform the user about Finnone access. User can access the
application with AD-ID and password.

Note - Above mentioned steps shall also be followed for any addition/deletion/modification in role name and role
description in Finnone.

2. M-CAPS Access: M-FI is a mobile based collection application which is used to generate electronic receipts by
executives for payment collection from delinquent customers.
Below steps shall be followed for giving M-CAPS access to Outsourced staff based out at Vendor’s premise:-

Steps No. Activities FPR

Request for M- 1 RA shall send a request on mail to Process team for M-CAPS access to the RA
CAPS Access user, as per the attached format
Encl:- ID creation format (Annexure 2)

Page 8 of 9
Mapping of 2 Process team shall raise an E-Ticket in ESM for mapping access of Office Process
Office-365 to 365 (Company portal access) to AD ID of the user and share the ticket no. Team
the AD ID with Wintel team exchange.support@yesbank.in over mail.
URL:- ESM
Wintel team shall map requested AD-ID with Office 365, send a Wintel
confirmation mail to requestor and close E-Ticket. Team
Mapping of 3 Process team shall add user in MDM-Intune portal for M-CAPS and Process
MDM-Intune confirm to RA over mail. Team
to the AD ID
For mFI, the “YBL-MDM-INTUNE-MOBILEAPP is “mCAPSROD-
ALLOW”
RA shall inform the user to download the Intune company portal RA
application from Play store to access the respective application.
User ID and password of the mobile application shall be same as of
desktop-based application

C. Entitlement Review:
Steps No. Activities FPR

Entitlement 1 On a quarterly basis, LAM team sends notification mail to all the RA/ LAM
review – employees to complete the Entitlement review for their team. Team
ARMS roles
The concerned RA needs to review the Application role access for its sub-
ordinates including Vendor, Vendor staff etc. wherever applicable and
approve the role if he wants to retain or reject if it has to be deleted, in
ARMS

Page 9 of 9