Kibana Timezone Configuration for Multi-Regional User Access

Kibana handles temporal data by storing timestamps in UTC and typically converting them to the browser's local time zone for visualization. While the Advanced Settings provide a global timezone override to standardize the display across the instance, this setting applies universally to all users regardless of their physical location.

In environments where teams operate across multiple regional time zones, a global override prevents the browser-based detection from functioning, while the default browser setting may lead to inconsistencies when discussing specific time-window boundaries during cross-regional collaboration.

• Is there a mechanism to define time zone preferences at the user or space level rather than the global instance level?
• How does the system resolve conflicts between a global timezone override and the local browser offset during date histogram aggregation?