Skip to main content

Attendance Readiness Storage

Audience​

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.

Reference Content​

Summary​

Attendance Service persists local employee profiles, shifts, policies and employee-shift assignments. The inspected source does not prove an automatic onboarding consumer that creates every new employee profile or assignment.

Readiness model​

Selected objects​

  • EmployeeProfiles represent attendance-local workforce references.
  • Shifts and AttendancePolicies provide schedule and rule configuration.
  • EmployeeShiftAssignments connect an employee reference to schedule configuration.

Integrity boundary​

Tenant filters scope the selected business objects. Assignment support indexes aid employee and schedule access. Cross-service employee existence is not enforceable with a database foreign key.

Not proven​

Automatic profile creation, mandatory initial shift assignment, effective-date overlap prevention and a persisted readiness decision were not confirmed. Attendance activation should therefore not be inferred from Employee creation alone.

Requires confirmation​

Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.

Source References​

  • microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
  • microservices/src/attendance-service/Application/Services/EmployeeProfileService.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Review cycle: Quarterly