How to trigger last working day based on Time Zone?

Overview

This update ensures that employee portal access is disabled based on the employee’s work location timezone, instead of a fixed timezone (IST).

Earlier, portal access was revoked based on IST (Indian Standard Time) for all employees. This caused issues for employees working in other regions (such as the US or UAE), where access was revoked before their actual last working day ended in their local time.

With this enhancement, access is now aligned to the employee’s own timezone, providing a more accurate and seamless exit experience.

Who can access this feature?

• HR/Admins managing employee exits
• System processes handling employee lifecycle events (exit/LWD)

How it works

Updated behaviour

• Portal access is disabled based on:
  • Employee’s work location → timezone
• If timezone is not available:
  • System defaults to UTC
• Access is revoked at the end of the employee’s Last Working Day (LWD) in their local timezone

Manual override

• If an admin manually disables access before LWD:
  • That action takes higher precedence
  • It will override system-based access rules
• All manual actions are:
  • ✅ Logged in the backend
  • ✅ Available for audit purposes

Key Benefits

• Ensures accurate access revocation timing
• Prevents confusion for employees in different regions
• Improves employee exit experience
• Eliminates dependency on a single timezone (IST)

Important Notes

• Access is always aligned to the employee’s assigned work location timezone
• If no timezone information exists: 
  • System falls back to UTC
• Manual access changes by admin will override automatic behaviour
• All overrides are tracked for audit and compliance

Example Scenario

Scenario 1: Employee in the US

• Employee LWD: 30 June
• Timezone: PST

Behaviour:

• Portal access remains active until end of day (PST) on 30 June
• Access is not revoked earlier based on IST

Scenario 2: Employee in UAE

• Employee LWD: 30 June
• Timezone: GST

Behaviour:

• Access is revoked at end of day (UAE time)
• No early revocation due to timezone mismatch

Scenario 3: Timezone not configured

• No timezone available for employee

Behaviour:

• System uses UTC
• Access is revoked based on UTC end of day

Scenario 4: Admin manually disables access

• Admin disables access before LWD

Behaviour:

• Access is revoked immediately
• System does not wait for LWD
• Action is recorded in audit logs