US-301: Employee Central Profile View¶

1. Story Title¶

View unified employee profile

2. Context / Background¶

HR Manager needs consolidated view for employee administration and compliance.

3. User Persona¶

Primary: Priya – HR Manager Secondary: Mark – Employee (self-view)

4. Problem Statement¶

Employee data fragmented; no single source of truth impedes updates & reporting.

5. Desired Outcome¶

Priya & Mark can access a structured profile with core fields (personal, employment, contact).

6. Business Value¶

Reduces administrative overhead; foundation for downstream HR features.

7. Scope (In / Out)¶

In: profile read view, edit for HR, self-service limited edit (contact info). Out: Custom fields (US-302), org chart (US-303).

8. Acceptance Criteria (BDD)¶

Scenario: HR views employee profile
  Given an employee record exists
  When HR opens the profile page
  Then all core fields are displayed

Scenario: Employee views own profile
  Given Mark is authenticated
  When he opens his profile
  Then he sees personal & contact info
  And employment-only fields are read-only

Scenario: HR edits profile
  Given Priya is on a profile
  When she updates contact number
  Then the change persists
  And an audit event is logged

Scenario: Unauthorized edit blocked
  Given Mark views his profile
  When he tries to edit employment start date
  Then an authorization error is shown

9. UX Notes / References¶

Tab layout: Overview | Employment | Contact. Read-only labels with edit icon for HR-only fields.

10. Data / Domain Model Impact¶

Employee entity fields enumerated; audit log event type EMPLOYEE_PROFILE_UPDATED.

11. NFR Touchpoints¶

Performance: profile load p95 < 400ms.
Security: field-level authorization check.
Observability: edit events traced with user + tenant.

12. Dependencies¶

US-101 (tenant & user baseline).

13. Risks & Mitigations¶

Risk	Impact	Probability	Mitigation
Over-broad editable fields	Data inconsistency	Medium	Explicit allowlist & role checks

14. Estimation Support¶

Endpoint + DTO
Authorization layer
UI views
Audit instrumentation

15. Analytics / Success Metrics¶

Profile completion ratio; edit frequency per HR user.

16. Rollout / Release Strategy¶

Initial read-only; enable edits after stable deployment.

17. Definition of Ready Checklist¶

Field list finalized
Authorization model confirmed
Acceptance criteria validated

18. Definition of Done Checklist¶

Automated tests cover scenarios
Audit events appear in logs
Docs updated

19. Open Questions¶

Which self-edit fields allowed at MVP?

Version: 1.0