UCPath Access Request Form Steps
-
Background and Introductions
As a UCR employee or manager, UCPath access consists of Employee and Manager Self-Service pages that can be viewed when logging into the UCPath portal. As long as an employee is in active HR status, or a manager has one or more employees reporting to them, no special access needs to be granted. These are considered dynamic roles.
When an employee’s job requires access to see other employee’s data outside of the manager/employee relationship, this is considered elevated access. UCPath elevated access requires an approval process according to the UCPath Operational Governance process that was adopted when UCPath was implemented as the UC Systemwide HR, Benefits and Payroll system at UCR. There are 3 UCR UCPath-Business Owners representing UCR Business and Financial Systems, Central HR and Central AP policies, processes and employees. Please reference the UCR UCPath Operation Governance document for more information.Prerequisite requirements must be met prior to elevated UCPath access being approved and granted. In addition, there needs to be a clear business need for each request.
With implementation of the UC Policy known as the UC Policy on Gender Recognition and Lived Name, UCR now requires anyone with access to an employee’s Legal and Lived Name to complete a Confidentiality Agreement, returning it to HRPolicy@ucr.edu for their personnel file, and completion of two eCourses in the UC Learning Center: Gender Recognition & Lived Name: An Introduction to Gender Awareness and UC Policy on Gender Recognition and Lived Name.
In addition, there may be UCPath system training that is required to understand the data in the requested pages. Please contact UCPathCSC@ucr.edu to determine if UCPath system training (view only or transactional) is required.
-
Access to Request Workflow
Note: the request submitted through the ServiceNow UCPath Access Request form is for Central Office roles only. This process does not apply to Department or SSC provisioned access at this time. Please see your SAA overseeing UCPath access for departmental and SSC roles.
Once the ServiceNow Request is submitted, it routes to the individual’s CFAO for approval as a Request Item (RITM). When approved, the RITM will route to a Watcher group with a Sub-task (SCTASK) to verify the formal EACS access name, verify required training is completed and the Confidentiality Agreement is on file.
The RITM will then route to the specific Business Owner for approval. If a denied decision is made at any decision point, the ServiceNow Request will be closed and an email note with the closing comments will be sent to the Requester/Submitter.
When the Business Owner approves, a new Sub-task is then created for the Application SAA. At UCR, the Application SAA is our Controller. The Controller has ultimate approval and grants access or provides an explanation as to why the request was not granted.
At each transition/decision point, an email is sent to the Requestor/Submitter with the latest update.
- Stage 1: Initiation