SCREEN 01 Β· AUTHENTICATION
Login β€” Housekeeping Staff
HK Staff is the most restricted role in the system. JWT issued with role: hk_staff, data_scope: own_only β€” they can only see their own tasks, attendance, payslip, and training records. Login does not start the shift β€” Face Recognition Punch-In at the site is required. No GPS tracking triggered on login.
POST /auth/loginrole: hk_staff data_scope: own_onlyReports to: SupervisorNo GPS on login
7:58
●●● 80%
🧹
HRM Panel
Housekeeping Staff App
CleanPro Services Β· v1.0
Mobile Number
+91 98765 44444
4-digit PIN
Login β†’
Issues? Contact your Supervisor
Login Screen
β†’
7:59
●●● 80%
Welcome
Meena Sharma
HK Staff Β· EMP-4421 Β· Sunrise Township
// JWT Token Issued
role: "hk_staff"
emp_id: "EMP-4421"
data_scope: "own_only"
exp: +1h | refresh: 7d
β„Ή
Login does not start your shift. Go to site and complete Face Recognition Punch-In to activate attendance.
your access scope
βœ“
Face punch in & out
Yes
βœ“
My assigned tasks
Yes
βœ“
My attendance & payslip
Read
βœ“
My training records
Read
βœ—
Other staff data / admin
403
Go to Face Punch In β†’
Welcome + Access Scope
β†’
8:00
●●● 80%
Home Screen
Meena Sharma Β· EMP-4421
MS
Meena Sharma
EMP-4421 Β· Sunrise Township A
Morning
8:00–4:00 PM
Not In
Punch-in needed
πŸ“Έ
Punch In
βœ…
My Tasks
After punch-in
πŸ“…
Attendance
πŸ’°
Payslip
🏠
Home
πŸ“Έ
Punch
βœ…
Tasks
πŸ‘€
Profile
Home Screen
SCREEN 02 Β· MODULE 3 & 4 Β· FACE RECOGNITION PUNCH IN
Face Recognition Punch In β€” 3-Step Process
Three sequential steps must all pass: GPS geo-fence check (within 300m) β†’ Liveness challenge (randomised blink or head-turn, in-memory only) β†’ Face match against 128-D Azure embedding (confidence β‰₯ 0.6). All three must pass for punch to be recorded. Failure in any step blocks the punch.
Step 1: Geo-fence checkStep 2: Azure Liveness API Step 3: /detect + /verify (β‰₯0.6)POST /attendance/punch-in on pass
8:00
●●● 80%
Punch In
Meena Sharma Β· EMP-4421
GPS βœ“
142m inside
Liveness
Checking...
Face Match
Pending
Step 2 β€” Liveness
πŸ‘€
Blink twice slowly
In-memory Β· Not stored Β· Anti-spoof active
GPSβœ“ 142m within 300m
Liveness challengeBlink (randomised)
Stored?No β€” in-memory only
Liveness Active
8:01
●●● 80%
Step 3 β€” Face Match
Azure Β· 128-D embedding
Matching face...
πŸ‘€
↔
Comparing with 5 enrolled photos
Azure /detect + /verify
PersonGroup: SITE-001
threshold: confidence β‰₯ 0.6
Enrolled photos5 (onboarding)
Embedding128-D vector
Pass thresholdβ‰₯ 0.6 confidence
Raw image storedNo β€” discarded
Retries3 max β†’ supervisor override
Face Match Running
8:01
●●● 80%
Anti-Spoof Logic
What gets blocked
πŸ›‘
Azure Liveness runs in-memory. It detects real vs fake face. Challenge randomised each time β€” prevents pre-recorded replay.
rejected by liveness
πŸ–Ό
Printed photo
No depth β€” blocked
Blocked
πŸ“±
Screen replay
Screen flicker detected
Blocked
🎭
Silicone mask
Texture anomaly
Blocked
βœ“
Real person β€” blink done
Passes liveness β†’ face match
Pass
challenge types (randomised)
πŸ‘
Blink challenge
Blink 1–2 times
Type A
↔
Head-turn challenge
Turn head left or right
Type B
β„Ή
Randomisation prevents pre-recorded video replay attacks β€” attacker can't know which challenge will appear.
Anti-Spoofing Detail
SCREEN 03 Β· MODULE 4 Β· GEO-FENCE CHECK
Geo-fence Validation β€” Step 1 of Punch-In
Before liveness or face match, GPS coordinates are validated against the site's configured geo-fence boundary (default 300m). If outside β†’ punch immediately blocked, FCM P1 alert to Supervisor + Admin, anomaly logged as ANOMALY_GEO. All three anomaly types β€” Geo, Ghost, and Duplicate punch β€” shown here.
GET /site/{siteId}/geofence300m default radius Breach β†’ ANOMALY_GEO + FCM P1Configurable per site by admin
8:00
●●● 80%
Location Check
Sunrise Township A
Inside βœ“
300m fence
Statusβœ“ Inside fence
Distance142m (under 300m)
GPS accuracyΒ±5m
Fence radius300m (admin set)
FormulaHaversine
βœ“ Proceed to Liveness β†’
Inside Geo-fence βœ“
8:02
●●● 60%
🚫
Outside Fence β€” Blocked!
524m from site Β· Punch denied
🚨
Supervisor + Admin notified via FCM P1. Event logged as ANOMALY_GEO with GPS coords + timestamp.
Your distance524m (224m over limit)
Punch statusBLOCKED
Anomaly flagANOMALY_GEO
AlertPOST /alert/geofence-breach
anomaly types in system
πŸ—Ί
ANOMALY_GEO
Punch outside fence β€” blocked
P1
πŸ‘»
ANOMALY_GHOST
Punched in Β· No GPS trail during shift
P2
πŸ“±
ANOMALY_DUP
Two punches from same EMP in <4 min
P2
Outside Fence β€” Blocked
SCREEN 04 Β· MODULE 3 Β· LIVENESS DETECTION
Liveness Challenge β€” Blink & Head-Turn
After geo-fence passes, a randomised liveness challenge (blink or head-turn) is presented. Azure Liveness API processes the live camera feed in real-time β€” entirely in-memory, nothing stored at this step. Randomisation prevents pre-recorded video replay. Failure shows a clear retry prompt. Both challenge types shown below.
Azure Liveness API Β· In-memoryChallenge randomised per attempt Blocks: photo / video / maskNothing stored on failure
8:01
●●● 80%
Liveness β€” Blink
Challenge Type A
Blink Challenge
πŸ‘οΈ
Blink twice slowly
Face centred Β· Good lighting required
ProcessingAzure Β· In-memory
Image stored?No β€” discarded
ChallengeBlink (randomised)
Blink Challenge (Type A)
8:01
●●● 80%
Liveness β€” Head Turn
Challenge Type B
Head Turn Challenge
↔
Turn head to the right
Direction randomised Β· 45Β° turn needed
Why randomised?
If challenge were always "blink", attacker could pre-record it. Randomisation forces a live real-time response that cannot be pre-recorded or replayed.
Head-Turn Challenge (Type B)
8:01
●●● 80%
Liveness Passed βœ“
Proceeding to face match
Real
βœ“
Real face confirmed. Proceeding to face match against your 5 enrolled photos in Azure PersonGroup.
GPS
βœ“ OK
Liveness
βœ“ Real
Face
Matching...
full punch-in flow
βœ“
GPS within 300m fence
142m Β· Inside fence OK
βœ“
Liveness blink passed
In-memory Β· Real confirmed
β†’
Face match running
Azure /detect + /verify
threshold β‰₯ 0.6
β—‹
POST /attendance/punch-in
GPS + timestamp + location photo β†’ S3
Liveness Passed β†’ Face Match
SCREEN 05 Β· MODULE 3 Β· PUNCH RESULT
Punch-In Result β€” Success, Fail & Override
Confidence β‰₯ 0.6 β†’ punch recorded with GPS, timestamp, location photo (S3). Shift activated, Supervisor notified via FCM. Confidence < 0.6 β†’ 2 retries allowed (3 total). After 3 fails β†’ Supervisor must manually override. Multiple punches supported β€” late arrival, mid-shift break, early departure. All logged separately.
POST /attendance/punch-in (on match)3 fails β†’ supervisor override GPS + timestamp + location photo β†’ S3FCM to Supervisor on success
8:01
●●● 80%
βœ“
Punched In!
8:01 AM Β· 8 July 2025
Confidence: 0.91 Β· GPS: 142m
EmployeeMeena Sharma Β· EMP-4421
Punch-in time08:01:14 AM
Face confidence0.91 βœ“
Location photos3://punch-ms-0801.jpg βœ“
Shift activatedYes βœ“
Supervisor notifiedFCM sent βœ“
πŸ””
Supervisor Vikram P. notified of your punch-in. Tasks are now available.
Punch-In Success
8:03
●●● 80%
βœ—
Face Match Failed
Attempt 3 of 3 β€” Override needed
⚠
3 consecutive failures. Supervisor override required. Vikram P. has been notified via FCM.
Attempt 10.43 β€” Fail
Attempt 20.51 β€” Fail
Attempt 30.38 β€” Fail
Common reasons for failure:
β€’ Poor lighting β€” move to bright area
β€’ New beard / glasses since enrolment
β€’ Camera lens dirty
β€’ Face too close or too far from camera
⏳
Awaiting supervisor override...
3 Fails β†’ Supervisor Override
8:05
●●● 80%
Shift Active
Morning Β· 8:01 AM – 4:00 PM
In
8:01
In
β€”:β€”
Out
4:00
Shift end
1h 10m elapsed6h 50m remaining
multiple punch records
β„Ή
Late arrival, mid-shift break, and early departure each generate a separate punch record β€” all validated with face + GPS.
↓
Late arrival
Punched at 8:18 β†’ 18 min late
Late
⏸
Mid-shift break
Out + back in β€” both recorded
OK
↑
Early departure
Punch-out before shift end
OK
Active Shift View
SCREEN 06 Β· MODULE 5 Β· DAILY TASKS
My Daily Tasks β€” Shift Assignment
After punch-in, HK Staff sees their task list for the shift β€” assigned by Supervisor before or at shift start. FCM push notification delivered with task list. Each task shows location, instructions, SOP reference, and due time. Staff marks done in app β€” optional photo evidence. Incomplete tasks at shift end auto-flagged to Supervisor and Field Officer.
GET /tasks/today/{empId}PATCH /task/{id}/complete FCM push at shift startReal-time sync to SupervisorIncomplete β†’ auto-flag
8:05
●●● 78%
My Tasks Today
Sunrise A Β· 8 Jul 2025
3/8
done
Completion3 of 8 tasks
βœ“
Sweep & mop lobby β€” Ground Floor
Done 8:25 AM Β· Photo βœ“
βœ“
Clean male restroom β€” Level 1
Done 8:52 AM Β· Photo βœ“
βœ“
Bin collection β€” Lobby
Done 9:05 AM
β†’
Mop Corridors B & C β€” Level 1
In progress Β· 9:10 AM
Clean female restroom β€” Level 1
Vacuum carpets β€” Lobby
Check chemical stock levels
!
Gym deep clean β€” 2nd day overdue
Supervisor flagged β€” must complete today
πŸ“· Done + Photo
βœ“ Mark Done
Task List
9:00
●●● 78%
Task Detail
Mop Corridors B & C
Active
Assigned bySupervisor Vikram P.
LocationLevel 1 Β· Corridors B+C
Due by10:00 AM
PhotoOptional
step-by-step instructions
1. Use blue mop for corridors
2. Floor cleaner at 1:20 dilution ratio
3. Mop away from doorways
4. Deploy wet floor sign before starting
5. Remove sign when floor is dry (~15 min)
πŸ“„
SOP: Floor Cleaning v2.1 Β§4.3 β€” Blue mop corridors only. Never use red (ICU) mop here.
βœ“ Mark Complete
πŸ“· + Photo
Task Detail View
4:00
●●● 35%
Shift End β€” Task Summary
8 Jul 2025
7
Done
1
Incomplete
Completion rate87.5%
βš‘
Gym deep clean incomplete β€” auto-flagged to Supervisor Vikram P. and FO Rajiv K. immediately.
β„Ή
Incomplete tasks are auto-reported via API at shift end. No action needed from staff β€” system handles it.
Proceed to Punch Out
Shift-End Task Summary
SCREEN 07 Β· MODULE 5 Β· TASK COMPLETION
Marking Task Done β€” With Photo Evidence
Staff marks tasks done in the app. Optional photo evidence captures the completed work area β€” supervisor sees real-time update. Photo captured in-app only, GPS + timestamp embedded. PATCH /task/{id}/complete syncs to supervisor immediately. Overdue tasks stay highlighted until resolved.
PATCH /task/{taskId}/completePUT /task/{id}/photo (optional) In-app camera Β· GPS taggedReal-time sync to Supervisor
9:45
●●● 78%
Mark Task Done
Mop Corridors B & C
πŸ“·
Photo is optional but recommended. Supervisor can confirm quality. GPS + time auto-tagged.
Capture Completion Photo
πŸ“Έ
Show the completed work area
In-app camera Β· GPS + time auto-tagged
TaskMop Corridors B+C Β· L1
Completed9:43 AM
Syncs toSupervisor real-time
APIPATCH /task/4421-03/complete
βœ“ Done
πŸ“· Done + Photo
Task Completion
9:46
●●● 78%
Task Confirmed
Synced to Supervisor
Done
βœ“
Task marked complete. Supervisor updated in real-time. Photo saved to S3.
Photos3://task-9421-L1.jpg βœ“
Supervisor seesImmediate
remaining tasks
Clean female restroom β€” Level 1
Vacuum carpets β€” Lobby
Check chemical stock levels
!
Gym deep clean β€” overdue
Next Task β†’
Task Confirmed & Synced
SCREEN 08 Β· KRA 1 Β· COMPLIANCE VIEW
Uniform & Safety β€” Staff View
HK Staff don't conduct their own check β€” the Supervisor photographs them during floor rounds. However, the app shows the staff member their current compliance status and any violations. Safety reminders from SOPs are surfaced here β€” wet floor sign, PPE, chemical protocol β€” reinforcing what was taught in training.
View-only β€” Supervisor captures photoViolation alerts visible to staff SOP-linked safety remindersPhoto tag: uniform_compliance
8:20
●●● 78%
My Compliance
Today Β· 8 Jul Β· Meena S.
Pass βœ“
today's uniform check
βœ“
Uniform worn correctly
Checked by Supervisor 8:15 AM
OK
βœ“
ID badge visible
Front pocket βœ“
OK
βœ“
PPE available β€” gloves + apron
In cleaning trolley βœ“
OK
safety reminders (from SOP)
!
Deploy wet floor sign before mopping
SOP: Floor Cleaning v2.1 Β§3.1
!
Wear gloves when using chemicals
SOP: Chemical Handling v1.4 Β§2.3
!
Use correct mop colour per zone
Blue: corridors Β· Red: ICU only
β„Ή
Supervisor checks your uniform during floor rounds. Violations will appear here if flagged.
Compliance Status
8:22
●●● 78%
Violation Alert
Previous violation Β· 3 Jul
Noted
βš‘
You had a violation on 3 Jul β€” No ID badge. Corrected on-spot. Repeat violations escalate to written warning.
violation log
!
No ID badge β€” 3 Jul
Corrected: spare badge issued
Fixed
βœ“
Uniform check β€” 8 Jul
All items passed βœ“
Pass
escalation policy
1st violation β†’ Verbal warning + correction
2nd violation β†’ Written warning logged
3rd violation β†’ Escalated to Field Officer
4th+ β†’ HR review initiated
β„Ή
Supervisor photo evidence tagged uniform_compliance is stored with your employee record in admin panel.
Violation Log & Policy
SCREEN 09 Β· MODULE 12 Β· GYROSCOPE MONITORING
Gyroscope & Activity Monitoring β€” Module 12
The app uses the device's built-in gyroscope and accelerometer to passively monitor staff movement during the shift. Detects unusual patterns β€” prolonged idleness (possible sleeping), abnormal sudden movement (possible fall or accident), or suspicious stillness when tasks are assigned. Alerts are sent to Supervisor and Field Officer automatically. Visible passively to staff.
Module 12 β€” Gyroscope / AccelerometerIDLE_DETECTED if still >20 min UNUSUAL_MOVEMENT on sharp jerkFCM P1 to Supervisor + FO
2:30
●●● 50%
Activity Monitor
Passive Β· Running in background
Normal
πŸ“±
Movement detection runs passively. You don't need to do anything β€” it monitors automatically while app is open.
live motion reading
ACCELEROMETER READINGS
X-axis0.34
Y-axis0.72
Z-axis0.18
StatusNormal movement βœ“
Last movement2:28 PM (2 min ago)
Idle threshold20 minutes
Alert onIdle or sharp jerk
Normal Activity Reading
11:42
●●● 62%
⚠️
Unusual Movement Detected
Sharp jerk at 11:42 AM β€” possible fall
🚨
Supervisor Vikram P. and FO Rajiv K. notified immediately via FCM P1. Are you OK?
MOTION READING β€” ALERT
X-axis3.82 !
Y-axis4.11 !
Alert typeUNUSUAL_MOVEMENT
Time11:42:38 AM
FCM sentSupervisor + FO Β· P1
βœ“ I'm OK β€” Dismiss
Need Help!
Unusual Movement Alert
2:15
●●● 50%
😴
Idle Detected
No movement for 32 minutes
β„Ή
Supervisor has been notified of idle status. Tap "I'm Active" to dismiss or confirm your status.
MOTION READING β€” IDLE
X-axis0.01
Y-axis0.02
Alert typeIDLE_DETECTED
Idle duration32 minutes
Threshold20 minutes
Supervisor notifiedYes Β· FCM P2
βœ“ I'm Active β€” Resume
Idle Detected Alert
SCREEN 10 Β· MODULE 3 Β· PUNCH OUT
Punch Out β€” End of Shift
At shift end, HK Staff completes the same 3-step face recognition process for punch-out. GPS, liveness, and face match all re-verified. Punch-out time recorded with GPS coordinates and location photo. Total hours calculated. Supervisor notified via FCM. Attendance record finalised for payroll engine.
POST /attendance/punch-outSame 3-step validation Total hours auto-calculatedFCM to SupervisorPayroll engine updated
4:01
●●● 35%
Punch Out
Shift ending Β· Face verify required
Face Verification
πŸ‘€
Verifying face for punch-out...
Same 3-step process as punch-in
Punch-in was8:01 AM
Current time4:01 PM
Expected hours8h 00m
GPSβœ“ 187m (within 300m)
Payroll flagOn punch-out complete
Punch-Out Verification
4:02
●●● 35%
πŸ‘‹
Shift Complete!
4:01 PM Β· Great work today, Meena!
Punched In08:01 AM
Punched Out04:01 PM
Total Hours8h 00m βœ“
Tasks7 / 8 complete
PayrollUpdated Β· 8h counted
Supervisor notifiedFCM sent βœ“
πŸ’°
Today's hours (8h) logged to payroll engine. Payslip generated on last working day of month.
Go to Home Screen
Punch-Out Complete
SCREEN 11 Β· MODULE 10 Β· OFFLINE MODE
Offline Mode β€” No Network Coverage
The HK Staff app handles no-network scenarios using SQLite local cache. Tasks are pre-loaded at shift start. Punch-in attempts use last known GPS (cached). Photos are queued for S3 upload. Task completions stored locally. Everything syncs automatically on reconnect. Offline sync marked in the attendance record.
SQLite local cachePhotos queued β†’ S3 on reconnect Last known GPS for punchSync on reconnect Β· offline_sync flag
10:15
●●● 65% (No Signal)
πŸ“΄
No Network
Offline mode active
πŸ“΄
No internet connection. App is running in offline mode. Your work is being saved locally and will sync automatically.
offline capabilities
Tasks loaded at shift start βœ“
Task completions saved locally βœ“
Photos queued β€” 3 waiting to upload
Punch-in uses last known GPS
No FCM notifications while offline
Local storageSQLite
Last GPS cached10:02 AM Β· 156m from site
Photos queued3 files waiting
Tasks saved5 locally stored
Offline Mode Active
10:45
●●● 65%
🌐
Back Online!
Syncing offline data...
πŸ”„
Network restored. Uploading 3 queued photos and syncing 5 task completions to server now.
sync progress
βœ“
5 task completions synced
PATCH /task/{id}/complete Γ— 5
βœ“
3 photos uploaded to S3
PUT /task/{id}/photo Γ— 3
βœ“
Attendance record flagged
offline_sync: true in attendance log
βœ“
Supervisor updated
FCM pushed β€” task completions visible
Offline duration43 minutes
Sync statusComplete βœ“
Attendance flagoffline_sync: true
Back Online β€” Sync Complete
SCREEN 12 Β· MODULE 3 Β· ATTENDANCE HISTORY
Attendance History β€” Own Records Only
Staff can view their own attendance records β€” punch-in times, punch-out times, late arrivals, absences, and GPS accuracy flags. data_scope: own_only means attempting to view another employee's records returns HTTP 403. Monthly summary shows working hours, absenteeism, and late count used for payroll calculation.
GET /attendance/{empId}/historydata_scope: own_only Monthly summary β†’ payroll input403 on other emp attempt
5:00
●●● 35%
Attendance History
Meena Sharma Β· July 2025
22
Days present
1
Absent
3
Late arrivals
176h
Total hours
this week
βœ“
Mon 7 Jul
In 7:59 Β· Out 4:01 Β· 8h 02m
Full
βœ“
Tue 8 Jul β€” Today
In 8:01 Β· Out 4:01 Β· 8h 00m
Full
!
Wed 2 Jul
In 8:18 Β· Late by 18 min
Late
βœ—
Fri 27 Jun
No punch-in Β· Absent
Absent
anomaly flags
πŸ”„
10 Jul Β· Offline sync
Network restored Β· Data synced OK
Sync
Attendance Records
5:02
●●● 35%
Monthly Summary
July 2025 Β· Payroll input
Working days26 (Mon–Sat)
Days present22
Absent1
Late arrivals3
Total hours176h 00m
Absenteeism %3.8% (under 15% threshold)
deduction triggers for payroll
Absent deduction: 1 day Γ— daily rate
Late deduction: 3 lates Γ— configured rate
Advance deduction: β‚Ή0 this month
These are inputs to payroll engine β€” full breakdown in payslip.
πŸ”’
data_scope: own_only β€” you can only see your own records. Attempting to view EMP-4401 returns HTTP 403.
Monthly Summary
SCREEN 13 Β· MODULE 9 Β· PAYSLIP
Monthly Payslip β€” Full Deduction Breakdown
Monthly payslip generated on the last working day of the month. Shows gross salary, all statutory deductions (PF 12%, ESI 0.75%), and non-statutory deductions (absent days, late arrivals, advance, dress allotment if applicable). Net pay shown prominently. Staff can download PDF. FCM notification when payslip is generated.
GET /payslip/{empId}/{month}PF 12% Β· ESI 0.75% Absent / Late / Advance deductionsFCM P4 on generationPDF download
5:10
●●● 35%
Payslip
Meena Sharma Β· EMP-4421
June 2025 Β· Generated 30 Jun
earnings
Basic Salaryβ‚Ή 15,000
HRA (House Rent)β‚Ή 5,000
Conveyance Allowanceβ‚Ή 1,500
Special Allowanceβ‚Ή 2,000
Gross Salaryβ‚Ή 23,500
statutory deductions
PF β€” Employee (12%)– β‚Ή 1,800
ESI (0.75%)– β‚Ή 176
non-statutory deductions
Absent β€” 1 day– β‚Ή 500
Late arrivals (3Γ—)– β‚Ή 150
Advance recovery– β‚Ή 0
Dress allotment recovery– β‚Ή 375
net pay
Net Pay (Take Home)β‚Ή 20,499
πŸ“„ Download PDF
July 2025
Payslip β€” June 2025
5:12
●●● 35%
Deduction Explainer
What each deduction means
Statutory (Government-mandated)
PF (Provident Fund) 12%: Saved for retirement. Company also contributes 12% on your behalf.

ESI 0.75%: Employee State Insurance β€” covers medical expenses for you and family.
Non-Statutory (Attendance-based)
Absent days: Per-day rate Γ— days absent.

Late arrivals: Configured rate per late incident (varies by company policy).

Advance: Salary advance recovered over months.

Dress allotment: Uniform provided by company β€” cost recovered monthly over contract period.
Generated onLast working day
Bank transferSBI ●●●●9821
FCM notificationP4 Β· on generation
Deduction Breakdown
SCREEN 14 Β· MODULE 7 Β· MY TRAINING
My Training Records β€” Skill Matrix View
HK Staff can view their own training history and current skill levels. Shows sessions attended, quiz scores, and which sessions are upcoming. Remedial flags appear here if quiz score was below 80%. Skill levels updated after each training session by the Trainer. Staff cannot modify their own skill levels β€” read-only view.
GET /training/history/{empId}Read-only Β· own data only Skill matrix visibleUpcoming sessions shown
5:20
●●● 35%
My Training
Meena Sharma Β· EMP-4421
my skill levels
Brooming & Mopping95%
Chemical Use82%
Infection Control74%
Machine Operation60%
Soft Skills78%
Safety & First Aid88%
upcoming sessions
πŸŽ“
Soft Skills β€” Guest Interaction
10 Jul Β· 11:00 AM Β· Mandatory
10 Jul
πŸŽ“
Safety & First Aid Refresher
15 Jul Β· 10:00 AM Β· Mandatory
15 Jul
Skill Matrix View
5:22
●●● 35%
Session History
All sessions attended
july 2025
πŸŽ“
Infection Control β€” 8 Jul
Attended Β· Quiz: 88% βœ“
Pass
πŸŽ“
Eco-friendly Practices β€” 6 Jul
Attended Β· No quiz
Done
πŸŽ“
Machine Operation β€” 5 Jul
Attended Β· Quiz: 80% βœ“
Pass
πŸŽ“
Chemical Safety β€” 3 Jul
Attended Β· Quiz: 85% βœ“
Pass
june 2025
πŸŽ“
Soft Skills β€” 12 Jun
Attended Β· Quiz: 78% βœ“
Done
πŸŽ“
Floor Cleaning Refresher β€” 2 Jun
Absent β€” not attended
Missed
β„Ή
Skill levels are updated by Trainer after each session. You cannot modify your own skill levels.
Training Session History
SCREEN 15 Β· MODULE 2 Β· DIGITAL ID CARD
Digital ID Card & Document Status
Digital ID card auto-generated after onboarding completion and admin approval. Contains staff name, employee ID, photo, site, designation, and QR code linking to the encrypted employee record. Staff can show this for identification at site. Document status (Aadhaar, PAN, police verification) visible here with expiry warnings.
Auto-generated post onboardingQR links to encrypted record Document expiry alertsGET /employee/idcard/{empId}
5:30
●●● 35%
Digital ID Card
CleanPro Services
MS
Meena Sharma
Housekeeping Staff
EMP-4421 Β· Sunrise Township A
Scan QR to Verify
EMP-4421 Β· ID: CPL-S-4421
Joined: 15 Jan 2025 Β· Valid: 31 Dec 2025
πŸ“₯ Save to Gallery
Digital ID Card
5:32
●●● 35%
Document Status
EMP-4421 Β· Expiry alerts
βœ“
All your documents are currently valid. You will be notified 30 days before any document expires.
document status
πŸ“„
Aadhaar Card
4521 XXXX 7890 Β· Valid βœ“
Valid
πŸ“„
PAN Card
ABCPD1234E Β· Valid βœ“
Valid
πŸ“„
Police Verification
Clearance cert Β· Valid until Aug 2026
Valid
🏦
Bank Account
SBI ●●●●9821 Β· Salary linked βœ“
Active
πŸ‘€
Face Enrolment
Azure Β· 5 photos Β· EMP-4421 βœ“
Enrolled
id card info
GeneratedPost admin approval
QR links toEncrypted employee record
Expiry warning30 days before doc expiry
Document Status
SCREEN 16 Β· MODULE 11 Β· NOTIFICATIONS
Notifications β€” Housekeeping Staff
HK Staff receives the most limited set of notifications β€” only things directly relevant to them. P3 events include task assignments, training session reminders, and document expiry warnings. P4 includes payslip generation. They do NOT receive P1 safety/security alerts, SLA breach alerts, or cross-site notifications.
Firebase FCM Β· Own data onlyP3 + P4 only No P1 security alertsTask + training + payslip only
8:05
●●● 78%
Notifications
Meena Sharma Β· Today
3
βœ…
Tasks ready for today
8 tasks assigned by Supervisor. Tap to view.
8:01
πŸŽ“
Training β€” Soft Skills Β· 10 Jul
11:00 AM Β· Conference Room Β· Mandatory attendance.
Yest.
πŸ’°
Payslip β€” June 2025 ready
Net pay β‚Ή 20,499. Tap to view and download.
30 Jun
πŸ“„
Reminder: Attend safety session
Safety & First Aid on 15 Jul. Don't miss it.
14 Jul
never received by hk staff
βœ—
SLA breach alerts
Supervisor + FO only
N/A
βœ—
Safety incident alerts
P1 β€” Supervisor + Admin only
N/A
βœ—
Inspection fail alerts
Field Officer only
N/A
Notification Center
8:06
●●● 78%
HK Staff Alert Guide
What you receive
P3 β€” On Event
β€’ Tasks assigned for today (shift start)
β€’ Training session scheduled reminder
β€’ Training session cancelled / rescheduled
β€’ Document expiry warning (30 days before)
P4 β€” Monthly / Informational
β€’ Payslip generated notification
β€’ R&R event β€” you won award!
β€’ Onboarding step completed
NOT received by HK Staff
P1: Geo-fence breach, safety incidents, SLA breaches, inspection fails β€” these go to Supervisor + FO + Admin only. HK Staff is the most protected role β€” sees only their own data.
πŸ”’
FCM notifications are user-scoped. No other employee's data or alerts are ever sent to your device β€” enforced at server level.
HK Staff Alert Priority Guide