System Audit is not for HR

[Shotza247]

This is too complicated for someone in HR to review, so we should create a system admin who will monitor platform performance and this data, to help the organization with digital transformation adoption.

[Shotza247]

Here are the clarifying questions before implementation:

• Q1: Who is the System Admin?
• Q2: What should System Admin be allowed to see?
• Q3: What credentials should we seed for the first System Admin account?
• Q4: Should System Admin manage users?
• Q5: What dashboards matter most for MVP 2?

I’d suggest by Codex:
platform adoption: logins, nominations submitted, reviews completed
behavioral network: who gets nominated most, cross-department nominations
approval health: bottleneck managers, rejected nominations, overdue approvals
review quality: draft vs submitted, missing comments, rushed reviews
talent insight: highly nominated employees, trusted peers, department collaboration patterns.

• Q6: Should this dashboard show sensitive review scores?
• Q7: Should we add audit events for logins and profile changes too?

[Shotza247]

Here are the clarifying answers before implementation:

• Q1: A: We create a completely new system_admin this is not an hr admin.
• Q2: A: some analytics should be anonymized/aggregated to protect trust in the 360 process, because the system admin doesn't find value in who nominated who.
• Q3: A: Create Seed data, for our System admin to have their own, name, email, temporary password, department, and job title etc.
• Q4: A: they only monitor audits/analytics, Hr-admin should can create/edit/delete employees, reset passwords(only for new hires/ newly added members by hr staff), change roles(during promotion cycles and internal reshuffling), and fix department/manager mappings?
• Q5: A: I agree with your recommendation completely on the design approach
• Q6: A: No. System Admin should monitor platform behavior without seeing actual review comments/scores. HR needs the scores, but System Admin only needs operational and behavioral metadata.
• Q7: A: Yes

There will be a ripple effect across the project after creating an entirely new role, for the DB mostly.