09.
USER ADMINISTRATION/
MANAGEMENT
Section
Section Description
Page
Recapitulate
205
09.01
Users Logged in (View the list of users)
206
09.02
User Forced Closure
206
09.03
Change User Status
208
09.04
Change User Type
209
09.05
User Sign-on Reset
210
09.06
Change Home Branch of User
210
09.07
Change Time Limit
211
09.08
Change Capability Level
User Types, Capability Levels and Transaction
Groups
212
09.00
Annexure
214
09. USER ADMINISTRATION/ MANAGEMENT
09.00 Recapitulate
This module facilitates the users to do the enquiry using the following features.
Users rights
Allow changing of password
Controlled management of user rights
Proper segregation of users duties
Types of Menus
In Core Banking environment Capability level, Transaction Group, User type are
the three types of menus which help in assigning proper menus and rights to
various users.
Capability level
It is a numeral from 0 to 9. It is similar to the passing of powers.
Transaction group
Numerals like 2,3,20 etc are available to the user (Cashier, Teller etc.)
User type
A numeral is assigned to a user (Officer/Staff) with specific role, for instance in a
Branch, a Branch Manager is assigned User Type: 45, Cash officer has User Type:
60 and the Accountant has User Type: 50. Generally, there will be only one person
with User Type: 50 and User Type: 60 in any branch. There may be any number of
users set up as User Types: 1 and User Type: 40 in a branch. As a rule, too many
officers should not be set up with User Type: 45; it is to be restricted to one or
two officers only in a branch. The officer with User Type: 45 will be able to unlock
the users who get locked out, change the capability level for a user in case of
officiating, etc.
User/ System Administration Menu option:
This option provides essential functions for any user such as ability to change
password, perform enquiries and do store and forward of offline transactions,
which are available to all users. This menu option is available only to officers who
have User Type: 45, 50 or 60.
User Id
All user IDs are created at CDC only. The User id for every employee is his PF
Index No. At the time of migration, the Branch Manager will fax a list of
employees at his branch, together with full name, PF Index No., and the role (such
as Field Officer, Single Window Operator, Cash Officer) to Core Banking
Department for creation of users.
205
Maker /Checker
Most of the menus under User Management have Maker /Checker functionality.
That means, one officer will perform the change (Maker), and another officer has
to authorize that change (Checker).
Note:
All the functions performed in User Management need to be recorded in a register
for the purpose of audit.
09.01 Users Logged In (View the list of users)
Steps Description
User Enquiry
Screen No
009600
To reach the User Enquiry menu Navigate the following:
User/ System Administration
Enquiry
User Enquiry (SCR:009600)
At the end of navigation, Branch Number field will be visible as shown in the
Screenshot 1. Type the branch code, and click on Transmit.
After keying-in the branch number, a list of user IDs and names of the Tellers
(users) logged in the Branch is displayed.
09.02 User Forced Closure
This option is used to log out a specific user from the system.
Steps Description
1
User Enquiry
2
User Forced Closure
Screen No
009600
009755
Sometimes a user status is shown as signed-on even when the user has not signedon. In such cases user forced closure option is required to be used. This kind of
situation can occur in cases where there is failure of UPS at a branch or due to
inadvertent operation the PC gets rebooted, or the user failed to sign out properly
etc. When the User tries to login, he gets an error message: SIGNED ON
ELSEWHERE, MULTIPLE TELLER LOGIN NOT ALLOWED. The message means, the
connection at CDC is still open for the user.
As a first step one need to identify the CDC terminal number of the user. Access
the user enquiry menu option
To reach the User Enquiry menu Navigate as follows:
User/ System Administration
Enquiry
User Enquiry (SCR:009600)
206
A screen as shown in the screen shot 1.0 is visible.
As shown in the Screen Shot 1.0, enter the user id in the User Number field for
e.g. 326306.
Screenshot 1
This is the CDC Terminal No.
In the above Screenshot 1, for instance, 1556 is a value for the field "Is Signed
Onto Terminal Number". This is the terminal number allotted at CDC for the user
326306 (in the above example). The terminal number (1556 in this example)
should be recorded or noted down.
As a second step, Navigate using the following options:
User/ System Management
Changes
User Forced Closure
(SCR:009755)
207
Enter the Password of the Officer who is performing the transaction.
Enter User ID of the person who should be logged out (e.g. 326306)
Enter the Terminal number noted in the previous step (viz. 1556)
Click on Transmit button.
A OK message Successfully logged out of the system is shown and the user can
login to the system as usual.
09.03 Change User Status
This option is used whenever a Teller goes on leave.
Steps Description
1
Change the User Status
2
Authorisation
Screen No
009764
Queue (Refer 14.01)
Whenever an employee goes on leave or is transferred, it should be ensured that
his/her ID is not usable. As a measure of security, the status of the user should be
made inactive.
For this purpose, an Officer with User Type 45/50/60 has to access the following
menu:
User/ System Management
Changes
Change User Status
(SCR:009764)
Enter the Teller/user ID in the New Status field
Choose option 09: Inactive
Click on Transmit button.
The Transaction will go to the Checker for authorization. After the checker
authorizes the transaction, the User ID will become inactive.
Note 1: The Teller concerned should have signed off, otherwise the following error
message is displayed 147: TELLER NOT CLOSED.
Note 2: Whenever an employee resumes duty, the officer with User Type 45/50/60
has to access this menu again, and change the status to Active.
208
09.04 Change User Type
This option is used when a user gets promotion or he/she is officiating.
Steps Description
1
Change User Type Permanently
2
Authorisation
Screen No
009763
Queue (Ref 14.01)
When a user gets promotion or officiating as Officer, Cash Officer etc, the roles
get changed. The corresponding change needs to be effected in the system.
For this purpose, an Officer with user type 45/50/60 needs to access the following
menu
User/ System Management
Changes
Change User Type Permanently
(SCR:009763)
Enter the Teller ID
Choose appropriate User Type as shown in the Table 1 depending on his/her
new role.
Click on Transmit button.
Table 1 : User types in a branch
01: Teller
A user who is not User Type 40, 50 or 60.
40: VPIS
Custodian
45: User Admin
An officer who can have overnight custody of Security Forms,
User with user management functions
UCO
50: Vault Teller
Accountant
60: Cash Officer
Cash Officer
The Transaction will go to Checker for authorization. After the checker authorizes
the transaction, the User type will get reset.
Note: Detailed steps relating to change of Accountant and Cash Officer are
explained in Chapter 6.
209
09.05 User Sign-On Reset:
This option is used to Reset the User ID.
Steps Description
1.
User Sign-on Reset
2.
Authorisation
Screen No
009760
Queue (Ref 14.01)
When the user forgets his password, or has made 3 unsuccessful attempts to login
with invalid password, the system suspends the user and does not let him login.
Hence the password of the user has to be reset.
To reach the option, navigate using the menu options as shown below:
User/ System Management
Changes
User Sign-on Reset
(SCR:009760)
Enter the Teller/user id.
Click on Transmit button.
The Transaction will go to Checker for authorization. After the checker authorises
the transaction, the password of the user will get reset to 111111. The user should
immediately login and change the password to something of his choice. Please
refer to Chapter 1 on how to frame strong passwords.
09.06 Change sign-on Branch Permanently
This option is used to change Home branch of User
Steps Description
1
Change Sign-on Branch Permanently
2
Authorization
Screen No
009762
Queue (Ref 14.01)
When the User gets transferred or is sent on Deputation to another Core branch,
Home branch of the user has to be changed. An Officer with User Type 45/50/60 in
the concerned branch changes the home branch of the user. This will enable the
user to login at the other Core banking branch where he/she reports.
To reach the option, navigate using the menu options as shown below:
User/ System Management
Changes
Change Sign-On Branch Permanently
(SCR:009762)
Note: Teller concerned should have signed-off.
210
Screenshot 2:
Enter the user number in the user number field as shown in Screenshot 2
Enter New sign-on Branch (Core Branch only).
Click on Transmit button.
The Transaction will go to Checker for authorization. After the checker authorizes
the transaction, the User will be able to login at the other branch where he/she
got transferred or sent on deputation.
Important Notes:
Only the relieving branch can change the Home branch of a Teller.
One EOD must pass for the change to take effect, before the User can login
at the new branch. In other words, if he/ she is relieved on any day and
his/ her Home branch also is changed the same day in the system, he/ she
cannot sign on at the other branch before the following day morning.
However, if the user on deputation has not logged-in at all on that day in
his/ her branch, then his/her Home branch can be changed and he/she will
be in a position to login at the other branch the same day.
In case the User is transferred to a Core banking branch, the above
procedure has to be followed. Note that the User-id need not be made
Inactive.
In case the User is transferred to a Non-Core banking branch,
(i)
User ID has to be made Inactive in the system as explained in 09.03
and
(ii)
The matter has to be reported to CDC.
09.07 Change Time Limit:
Steps Description
1
Change Time Limit
2
Authorisation
Screen No
009980
Queue (Ref 14.01)
211
Normally the Time Limit for the user will be set at CDC. When the Time Limit has
to be changed in the branch the option is available with the Officer with User Type
45/50/60. Suppose the branch working hours are from 9.00 a.m. to 6 p.m, then it
is sufficient that the single window operators are allowed to login by 8.30 a.m.
and not work beyond 9.00 p.m. in the system.
To reach the option, navigate using the menu options as shown below:
User/ System Management
Changes
Change Time Limit
(SCR:009980)
Screenshot 3
Enter Teller ID in the User No field of the Screenshot 3.
Enter the Start Time as 0830 (i.e. the user cannot login before 8.30 a.m)
and End Time as 2100 (i.e. the user cannot work beyond 9 p.m).
Click on Transmit button.
The Transaction will go to Checker for authorization. After the checker authorises
the transaction, the User will be able to work within the set Time Limit only. This
is as a measure of security.
Note: The time limit to be set for each user will vary depending on his role and
the branch working hours.
09.08 Change Capability Level:
Steps Description
1
Change Capability Level
2
Authorisation
Screen No
009761
Queue (Ref 14.01)
Note: The Teller concerned should be logged in.
When a user gets promotion or officiating as Officer, Cash Officer etc, the roles
get changed. The corresponding change needs to be effected in the system.
For this purpose, the Officer needs to access the following menu
212
User/ System Management
Changes
Change Capability Level
(SCR:009761)
Screenshot 4
Enter the Teller ID in the User Number field in the Screenshot 4.
Choose the appropriate Capability, Group capability. (Please refer to the
Chart at the end of the chapter). And make the next field as YES
depending on his/her new role.
The Transaction will go to Checker for authorization. After the checker authorises
the transaction, the User has to login fresh and he/she can work with the new
capability. The Teller concerned should logoff and then login again to check that
the new capability level has taken effect.
Note: This change will be temporary in nature (that is, valid for that day only).
For permanent change of Capability level, a formal request has to be sent to CDC.
Note1:
The following information will now be shown on a successful log-on(Screen
no.032026):
1.Date and time of the previous successful logon.
2.Details of any unsuccessful login attempts since the last successful logon.
Note2:
GENERAL Autotime out settings: If there is no activity on the screen by the teller
upto 180 seconds auto time-out will happen.
213
Core Banking Solution
User Types, Capability Levels and Transaction Groups
(sorted by Transaction Group)
Sl.
No.
Description
User
Transaction User
Capability Group
Type
01
Enquiry user
10
02
Cashier
03
Teller
04
Data Entry Operator
05
Senior Assistant
06
Special Assistant
07
Cash Officer with User Admin
60
08
Passing Officer with User Admin
10
45
09
Field Officer with User Admin
11
45
12
45
12
50
10
11
Passing Officer with Unlimited Powers
With User Admin
Accountant (Vault Officer) with
User Admin
12
Divisional Manager with User Admin
13
45
13
Branch Head with User Admin
14
45
14
Cash Officer without User Admin
16
60
15
Passing Officer without User Admin
17
16
Field Officer without User Admin
18
19
19
50
19
Divisional Manager without User Admin 8
20
20
Branch Head without User Admin
21
17
18
Passing Officer with Unlimited Powers
without User Admin
Accountant (Vault Officer) without
User Admin
214
Core Banking Solution
User Types, Capability Levels and Transaction Groups
(sorted by Role)
Sl.
No.
Description
User
Transaction User
Capability Group
Type
01
Enquiry user
10
02
Cashier
03
Teller
04
Data Entry Operator
05
Senior Assistant
06
Special Assistant
08
Passing Officer with User Admin
10
45
09
Passing Officer without User Admin
17
12
45
19
10
11
Passing Officer with Unlimited Powers
with User Admin
Passing Officer with Unlimited Powers
without User Admin
12
Cash Officer with User Admin
60
13
Cash Officer without User Admin
16
60
14
Field Officer with User Admin
11
45
15
Field Officer without User Admin
18
12
50
19
50
16
17
Accountant (Vault Officer) with
User Admin
Accountant (Vault Officer) without
User Admin
18
Divisional Manager with User Admin
13
45
19
Divisional Manager without User Admin 8
20
13
Branch Head with User Admin
14
45
20
Branch Head without User Admin
21
**********
215
