UNDERSTANDING YOUR CURRICULUM
The UCLA UCPath team is committed to implementing a security model that grants the appropriate level of visibility and access to each employee using UCPath.
UCPath will utilize the current ‘single sign-on’ framework via Shibboleth. UCLA Identity Management System will align the UCLA UID with the PeopleSoft Employee ID. All employees will be granted access to the UCPath Portal for employee self-service as part of cutover and new employees will automatically be granted access to the UCPath Portal.
Access in UCPath for Transaction roles will be granted in the Distributed Administrative Computing Security System (DACSS). Departmental Security Administrators (DSAs) will use DACSS to authorize what a user can do, and which departments a user can see (e.g., Department 123400).
Human Capital Management (HCM)
Responsible for employment, leaves, absences, compensation, and separations transactions
Pay Administrator (PA)
Responsible for payroll transactions
General Ledger (GL)
Responsible for funding, direct retro, and budget transactions
In order to be provisioned in UCPath you must complete the full training curriculum associated with your UCPath role/roles. Within each category in UCPath, there are three role types:
Initiator - responsible for entering transactions into UCPath and submitting for approval
Approver - responsible reviewing and approving transactions
Inquiry - has view-only access to specific pages in UCPath
There are three additional, less common roles. There are three roles that are for specific purposes and don’t fall into role categories or role types:
AWE Administrator: Monitors transaction routing and resolves bottle-necks; Can re-route transactions but cannot approve
Global Administrator: Responsible for resolving complex transactions; For central office (e.g. Central Human Resources) use only
Global Administrator: Finance: Responsible for resolving complex finance transactions; For Corporate Financial Services use only