Zoomed Image

User Timezone Display

xAssets Configuration Guide
Settings

User Timezone Display

xAssets can display dates and times in each user's local timezone rather than the server's timezone. This feature is essential for organisations with users across multiple time zones, ensuring that timestamps for asset changes, discovery events, and audit records are meaningful to each user regardless of their location.

How It Works

The xAssets application server stores all dates and times in the server's local timezone (or UTC, depending on the server configuration). When the User Timezone Display feature is enabled, the web interface automatically converts these timestamps to the user's local timezone before displaying them.

The conversion is based on the timezone configured in the user's browser or operating system. The system detects the user's timezone automatically -- users do not need to configure their timezone manually within xAssets.

What Is Converted

Timezone conversion applies to date-time fields displayed throughout the application:

Area Examples
Query results Date columns in asset lists, incident lists, and other query results
Asset editing forms Last modified date, creation date, discovery date
History and audit logs Timestamps showing when changes were made
Dashboard displays Date-based KPI tiles and chart labels
Batch job logs Job start and completion times

Date-only fields (fields that do not include a time component, such as Warranty End Date or Purchase Date) are not converted, as they represent calendar dates that are timezone-independent.

Configuration

Enabling User Timezone Display

  1. Navigate to Admin > Settings
  2. Search for the timezone-related setting
  1. Set the value to Yes to enable timezone conversion
  2. Click Save

The change takes effect immediately for all users on their next page load.

Verifying the Setting

After enabling the feature, you can verify it is working by comparing the timestamp shown in the web interface with the server's local time. If you are in a different timezone from the server, the displayed time should reflect your local time.

How the User's Timezone Is Detected

The system uses the timezone reported by the user's web browser, which is derived from the operating system's timezone setting. This means:

  • Users do not need to select a timezone within xAssets
  • If a user travels and their laptop's timezone changes, the displayed times adjust automatically
  • The detection works with all modern browsers (Chrome, Edge, Firefox, Safari)

Important Considerations

  • Server logs vs displayed times. Server-side log files and database records remain in the server's timezone. Only the web interface display is converted. If you are comparing a displayed timestamp with a database value or server log entry, be aware of the timezone offset.

  • Shared screenshots. When users in different timezones share screenshots of the application, the same event may show different times. This is expected behaviour -- each user sees the time in their own timezone.

  • Daylight Saving Time. The conversion automatically accounts for Daylight Saving Time (DST) transitions in both the server's timezone and the user's timezone.

  • Historical dates. Dates from before a DST rule change are converted using the rules that were in effect at that time, ensuring historical accuracy.

Tips

Tip: If your organisation operates in a single timezone, you may not need this feature. Enabling it adds no overhead but also provides no benefit when all users and the server share the same timezone.

Tip: When troubleshooting issues that involve timestamps (e.g., "discovery ran at the wrong time"), ask the user to confirm their local timezone and compare it with the server timezone. The batch job log on the server shows times in the server's timezone, while the user sees them in their local timezone.

Tip: For reporting purposes, if you need all users to see the same time regardless of their timezone (e.g., for compliance reporting where server time is the standard), consider disabling this feature and documenting the server timezone for your users.

  • Settings -- navigating and editing system settings
  • Users -- managing user accounts
  • Batch Jobs -- scheduling and monitoring batch operations