NetLock RMMNetLock RMM Docs
IV — Administration

Globalisation

Date and time format, how timestamps are stored (local time or UTC), the instance display timezone, the default language and custom language files. Users can override the timezone and the language for themselves.

Globalisation

Settings → Globalisation at /settings/globalization configures how NetLock RMM formats and renders dates and times across the Console, which clock timestamps are stored on, and which language the Console uses by default. Users can override the timezone and the language for their own account on Account → Home (/account/home).

Globalisation page with the Date/Time Format dropdown open and a live preview below it

A.5.1 Date and time format

Date/Time Format is a dropdown with seven presets. A live preview renders directly beneath the dropdown, updating as you change the selection, so you can see the chosen format applied to the current date and time before saving.

Preset labelExample
ISO2026-03-18 14:30:00
EU18.03.2026 14:30:00
UK18/03/2026 14:30:00
US03/18/2026 02:30:00 PM
Textual month18 Mar 2026 14:30:00
Slash ISO2026/03/18 14:30:00
Dashed day-first18-03-2026 14:30:00

Pick the preset that matches your team's convention and click Save. The change is applied Console-wide immediately; a browser refresh is not required.

The selection is deployment-wide. Users and tenants cannot override it, so choose a format your entire admin team is comfortable reading.

A.5.2 Time and timezone

The Time & timezone card decides two separate things: which clock timestamps are stored on, and which zone they are shown in.

Time mode: local or UTC

Every timestamp in the database is stored on one clock, the instance's time mode:

  • local: timestamps are stored in the server's local time. Installations that have never been switched to UTC use this mode. Timestamps are shown exactly as stored, in server time. No timezone setting has any effect in this mode, neither the instance display timezone nor a user's own timezone. Both can be set ahead of the switch; the page and Account → Home say so next to the field.
  • utc: timestamps are stored in UTC, and the Console converts them to the display timezone of the signed-in user. New installations start in this mode.

The alert at the top of the card shows which mode the instance is in. While the instance is still in local mode, the card offers Switch to UTC:

  1. Choose the Display timezone. The switch refuses to start without one, because every screen would otherwise jump by the server's offset.
  2. Click Switch to UTC. The confirmation dialog lists the consequences and requires the literal text UTC to be typed.
  3. On confirm the time mode and the zone shown in the field are saved together and written to the audit log. The Console follows immediately, including sessions that are already open; the backend picks the change up within a minute.

The switch is one-way. Run it inside a maintenance window. Directly after the switch, alerts and scheduled work can trigger once at an unexpected time. Rows written before the switch are not converted and appear shifted by the server's previous UTC offset; in tables with a retention period they disappear over time.

Display timezone

The zone a timestamp is rendered in is resolved per user, in this order:

  1. The user's own timezone, chosen on Account → Home with the Timezone field and saved with Update. The browser's zone is offered there as a one-click suggestion but never applied on its own. Leave the field empty to follow the instance.
  2. The instance Display timezone on this page.
  3. UTC, when neither is set.

Only zones from the list can be saved; an unknown zone is rejected. A changed zone applies on the next render of the Console: the instance zone in every open session, a user's own zone in the session it was saved from. Other open tabs of the same user pick it up after a reload. Lists and charts that are already loaded show the new zone once they are refreshed.

Messages that leave the instance (e-mail, Microsoft Teams, Telegram, ntfy, the ticket webhook) are produced without a signed-in user and always use the instance display timezone, naming the zone next to the time.

A.5.3 Language

Default Language is the language used for users who have not chosen their own; it also sets the number and date formatting culture. Users pick their own language on Account → Home.

Language Files lists the shipped and custom language files. Shipped languages are embedded; to customise strings or add a language, place a JSON file in internal/lang/ and click Reload language files. Download en-US template provides the English baseline, Import language runs a guided import with a completeness check against it, and Upload language file saves a file (including a partial override with only the changed keys) without that check.

A language file also carries the presets for the end-user texts of a policy (section Classes.Policies.Policy_Text_Presets, see §6.5.1). All shipped languages include them.

A custom language is offered in the policy editor's Text language menus once its own file translates every text of that section; an incomplete section is not filled up from English or from a base language, so the language is not offered until the file is complete. The import's completeness check counts missing preset texts like any other key.

A partial override of a shipped language can change single preset texts; the change appears in the menus after Reload language files. Applying a preset copies the texts into the policy, so a later change of the language file does not alter policies that were already saved.

A.5.4 What this page does not configure

  • Number format. Numeric formatting follows the language culture; there is no separate thousands-separator or decimal-separator selector.
  • First day of the week. Week-start conventions are not configurable.
  • Currency. Currency formatting for reports and invoicing is not configured here.

Permissions

CapabilityRequired flags
View and change Settings → Globalisationsettings_enabled, settings_globalization_enabled
Set your own timezone and language on Account → Homenone — every signed-in user can change their own account
  • Chapter A.2.2 — Maintenance. Each maintenance window carries its own timezone; the format chosen here only affects display.
  • Chapter 12 — Events & Audit. Event timestamps are rendered using the format and the display timezone configured here.