ADS Domain Roles Required for PeopleTools Application Users

Last updated April 16, 2009

The software that is used to perform functional user, project member or developer tasks in PeopleTools applications resides on shared network resources. Access to those resources requires that a user have the necessary privileges to access them, and this is provided through the assignment of Windows Network "roles" to a user's ADS account (regardless of their 'home' domain).

The list below details which roles are required for a user to perform a specific function. When requesting privileges for a new user, please use the appropriate Role Name(s) as per below.

A convention exists to denote these roles:

Primary roles are prefixed with a "p"
Secondary roles are prefixed with an "s"

Note that a user may only be assigned one primary role from any one project, so a change in project responsibility requires the old role to be revoked when the new role is granted.

A user may have any number of secondary roles.

At the time of this writing, the applications in production are of the following versions:

CECS: JobMine 8.1

HRMS: Human Capital Management 8.9

SISP: Learning Solutions 8.1

CECS Project -- JobMine 8.1

User Type	Role Name	Drives Mapped
Functional Users	Web access only—no roles required	none
Functional Project Members	pCECS_Project_Member	K:
Developers/Technical Leads	pCECS_Project_Developer	K: M: L: P:

Report Users	sCECS_Report_User	none

HRMS Project -- Human Capital Management 8.9

User Type	Role Name	Drives Mapped
Functional Users	pHRMS_Functional_User	P:
Functional Project Members	pHRMS_Project_Member	K: L: P:
Developers/Technical Leads	pHRMS_Project_Developer	K: M: L: P:
IAP Project Members	pHRMS_IAP_Member	K: L: P:
Enterprise Learn Mgmt Members	pHRMS_ELM_Member	K:

Budgets Users	sHRMS_Budgets_User	Q:
Enterprise Learn Mgmt Reports	sHRMS_ELM_Reporting	K:
Pension Plan Advisors	sHRMS_Pension_User	U:
TD Transmission Users	sHRMS_Direct_Deposit	none

SISP Project -- Learning Solutions 8.1

User Type	Role Name	Drives Mapped
Functional Users	pSISP_Functional_User	P:
Functional Project Members	pSISP_Project_Member	K: L: P:
Developers/Technical Leads	pSISP_Project_Developer	K: M: L: P:

SISP2 Processing	sSISP_ProcSched	none
SISP2 Processing (Financial Aid)	sSISP_ProcSched_FA	none

Oracle Database Access

If a PC user requires access to Oracle databases, but is not a user of any of the PeopleSoft applications above, they will then need explicit access to the shared Oracle database names table:

User Type	Role Name	Drives Mapped
Non-PeopleSoft Oracle Database User	sOraNet_User	P:

Note that Oracle database names access is included with all the primary PeopleSoft roles above.