PS User Security Setup
PS User Security Setup
Government of India
Contents
1
GENERAL........................................................................................................................................5
INTRODUCTION...........................................................................................................................5
CREATION OF DEPARTMENTS....................................................................................................21
CREATION OF DEPARTMENT TREE............................................................................................22
RUNNING APPLICATION ENGINE FOR UPDATING DEPARTMENT SECURITY.............................26
CREATION OF DATA PERMISSION LISTS.....................................................................................27
ATTACHING VARIOUS DEPARTMENTS TO DATA PERMISSION LISTS............................................28
ATTACHING DATA PERMISSION LIST TO USER PROFILE.............................................................29
ABBREVIATIONS........................................................................................................................30
Confidential
Confidentiality Statement
This document contains information that is proprietary and confidential to Tata Consultancy
Services Limited, which shall not be disclosed outside Tata Consultancy
Services Limited transmitted, or duplicated,
used in whole or in part for any purpose other than its intended purpose. Any use or
disclosure in
whole or in part of this information without express written permission of Tata Consultancy
Services Limited is prohibited.
Any other company and product names mentioned are used for identification purposes only,
and
may be trademarks of their respective owners.
Copyright 2006, Tata Consultancy Services (TCS) Limited.
Warning
This is a hard copy of a document maintained on electronic media. It may not be the latest
version. Kindly ascertain the latest version from the Document Master List available with the
Project Manager.
Confidential
Notice No.: 1
Customer: For Internal TCS usage
Project: PeopleSoft Implementation for Establishment Functions
Document details:
Name
Version No.
Description
1.0
New
page No.
Revision
Description
Revision details:
Action
taken
(add/del/ch
Preceding
page No.
Prepared by:
Priyanka Sharma
Date:
5-Apr-06
Approved by:
Sangeeta Anil
Date:
6-Apr-06
Authorized
by:
Peplesoft CoE
Date:
Confidential
1 General
Process Id.
Process Name
Owner
TCS Consultant
Date
PS_SECURITY
PeopleSoft User Security Setup Guidelines
TCS
Ms. Priyanka Sharma
05/04/2006
2 Introduction
For any software application, sanctity of the data maintained is important. Not all users of the
application need to have access of all screens. It is important that right data is available to the
right person only. For this purpose, user security aspect comes into play. The PeopleSoft
User Security Setup Guidelines Document outlines the procedure of setting up security at
user level.
There are two levels of security in PeopleSoft application: First, what all screens a PS user
can access and, Second, whether user can see the data of other user or not .If yes, to what
extent. The first level of security is referred as Page level security and second level is called
Row level or data permission Security.
Confidential
Navigation: PeopleTools > Security > Permission & Roles > Permission Lists
Confidential
In General Tab, all components that user can access are defined.
One can either key in the name of menu or select the menu using the Prompt button. More
menu can be added using + button.
Confidential
Click on edit components link to give access of various components under the particular
Menu.
Confidential
Click on Edit pages to give access to various pages under the particular component.
Confidential
Convention for naming a permission followed in MCA project has been following:
MCA_<Module Name>_<Role in that module>
For e.g. for a person having role of EIS admin, permission list name is MCA_EIS_ADMIN or
for an employee using loans functionality, permission list name is MCA_LOANS_EMP.
There are some basic permission lists (delivered by People Soft) to be given to all irrespective
of role. These are following.
HCSPCMPINT
HCSPMSGCHN
HCSPMSSCHG
HCSPPERSON
Standard Personalizations
HCSPPRCS
HCSPQUERY
HCSPSIGNON
HCSPWEBLIB
Apart from these, following are specific permission lists prepared for MCA:
1. MCA_WORKLIST: For an user accessing worklist
2. MCA_REPORTS: For an user who need to generate reports
3. MCA_PORTAL_PER: For accessing portal icons
Confidential
10
Following screen will open. By default, General tab will open. Give description of role in the
following tab.
Confidential
11
In Permission Lists tab, give various permission lists that this particular role can access.
Confidential
12
For roles also, convention followed has been same as permission list.
MCA_<Module Name>_<Role in MCA>
All employee permission list and basic permission lists have been given in one particular role:
MCA_ESS_BASIC
Confidential
13
Give Primary Permission List and Row Security permission list (these will be explained in detail in later
part) applicable to the user.
Confidential
14
In ID Tab, for defining user ID for the employee, select ID type as Employee. In EmpID field, give the
employee ID of the person for which user profile is being created.
In Description field, give the description of the user profile. (If you click on Set Description link then
name of the employee will appear for which ID has been created.)
15
Confidential
16
Confidential
17
Confidential
18
Confidential
19
In case, permission list does not appear even if access has been given, then simply click on Save
button. The required Permission List will be incorporated in the folder.
Confidential
20
Confidential
21
Confidential
22
Confidential
23
Confidential
24
It is mandatory to create one root department. All other departments will be covered under this
department.
In MCA, one main root department has been created and then all other departments have been created
according to hierarchical structure. Then, root departments are created for each office. Under the root
department for a particular office, all other departments for that office have been created. In technical
parlance, Root department of an office is the parent department and other departments in that office are
child departments for that office.
Confidential
25
Every time, there is some modification in department tree (Addition, modification or deletion of
departments from department tree), one has to run this application engine.
Confidential
26
All data permission list have been prefixed with MCA_DP_<BU Name>_Additional description.
Confidential
27
Any employee having a particular permission list can access employees having departments (and child
departments of these departments) defined in that permission list.
Confidential
28
Confidential
29
5 Abbreviations
Sr. No.
1.
2.
3.
4.
5.
Abbreviation
Definition
MCA
BU
EIS
HRMS
PS
Confidential
30