AWS connect documentation change
Summary
Added timezone display logic explanation for agent calendars
Security assessment
Documentation update clarifies timezone prioritization logic for scheduling display. No security-related content or implications are addressed in these changes.
Diff
diff --git a/connect/latest/adminguide/scheduling-view-schedule-agents.md b/connect/latest/adminguide/scheduling-view-schedule-agents.md index f46fd4bf3..9dfc0e576 100644 --- a//connect/latest/adminguide/scheduling-view-schedule-agents.md +++ b//connect/latest/adminguide/scheduling-view-schedule-agents.md @@ -30,0 +31,9 @@ The following image shows a sample schedule in the agent workspace. +The Agent Calendar displays times according to the following prioritized timezone logic: + + * Agent-specific timezone — If the administrator has explicitly configured a timezone in the agent's staff rules or profile settings, this timezone is used. + + * Fallback: Agent's local device timezone — If no agent-specific timezone has been configured, the calendar uses the timezone detected from the agent's computer or browser settings. + + + +