Page Comparison

The following row-based security has been implemented with the Employee Activity Hub (EAH) on top of standard Activity Hub security.

UCPath transactors: EAH data access mirrors role and row-level security access in UCPath.
EAH data consumers and EAH report developers who are not UCPath transactors: data access must be requested and approved as part of an exception provisioning process.
Labor Ledger data: all approved EAH data consumers and report developers have access to all rows.

...

Running an EAH report without row-level security that has been built by your local report developer: ask your developer what Active Directory (AD) group your DSA should add you to in order to gain access to the report.
Running HR/Payroll reports found at reports.ucsd.edu: fill out the UCPath Reports Access Request form to request:
1. Access to HR/Payroll reports. Repeat for each group.
2. DOPE and UCPath-Oracle Salary Reconciliation access.
3. Additional departmental access.
Building reports in Cognos or Tableau using EAH: complete the Employee Activity Hub Report Developer Access Request.
1. EAH Report Developers can request additional departmental access via this form.
Running an EAH report built by your local report developer that relies on row-level secured view(s): fill out Employee Activity Hub Report Consumer Access Request and request your report developer add you to the AD group that has access to their reports.
1. EAH Report Consumers can request additional departmental access via this form.
Running the HR/Payroll report and developing EAH reports: fill out both #2 and #3 from above.
Running local EAH reports and developing EAH reports: fill out both #3 and #4 from above.
Running HR/Payroll reports, running local reports and develop EAH reports: fill out #2, #3 and #4.
Developing data integration: read this page and follow the steps: https://collabucsdcollab.ucsdatlassian.edunet/wiki/display/AH/How+to+Get+Activity+Hub+Data

Viewing reports that use blended data

...

...