Configure localization

The Localization tab is where you set the default timezone for your whole organization and see the display language and regional format Bulk uses. A timezone is the regional clock Bulk reads a moment against, the same instant reads as a different wall-clock time in Gotham than in Chicago. The locale is the language and regional formatting (how dates, times, and numbers are written). Setting a clear organization timezone gives Bulk one sensible default clock to fall back on when no more specific timezone applies.

You reach it inside the Organization settings page. Open Settings › Organization › Settings (/settings/organization/settings) and select the Localization tab. The Settings page shows a Localization section with Timezone, a read-only Locale, and a date/time preview.

Before you startCopy Anchor Link

You need permission to save changes. Saving on this tab requires the Edit organization settings permission (organization.update), which lets you change organization-wide settings such as the name and localization. In the default roles this permission belongs to the Super user (Owner) role. Other roles, including Entity admin, can open the tab and see the form, but an attempted timezone change will be rejected without that permission. If you are unsure, ask an Owner to make the change or to grant you the permission.

This is an organization-wide default, not a per-plant setting. In Bulk a plant (also called an entity) is a single manufacturing site, and each plant carries its own timezone. The value you set here is the organization's default, which is separate from the timezone attached to any individual plant. See Manage entities for the per-plant list.

Each plant's timezone is fixed when that plant is created. Bulk uses it for records owned by that plant, so a building's calendar does not change later because an administrator edits a setting. The organization also has one shared rule for when a week starts; changing plants or plant timezones does not create different week numbers.

Calendar-only values such as required dates, due dates, and inspection dates stay on the selected YYYY-MM-DD day. They do not move when someone opens the record or prints it from a computer in another country. Event values that include a time, such as received, completed, or approved timestamps, keep their exact recorded moment and are displayed in the appropriate timezone. Personal schedules use your saved user timezone when available, with the organization timezone as the fallback.

What you can setCopy Anchor Link

TimezoneCopy Anchor Link

The Timezone selector holds a curated list of common IANA timezones. IANA is the standard timezone database, where each zone is written as region and city, such as Europe/London or America/New_York, plus plain UTC. The field's hint reads Used for dates and times across the organization. Open the selector and choose the zone that matches where your organization is based.

The list is a common subset, for example UTC, Europe/London, Europe/Paris, Europe/Berlin, America/New_York, America/Chicago, America/Los_Angeles, Asia/Tokyo, Asia/Singapore, and Australia/Sydney, rather than the full IANA database. If your exact city is not listed, pick the nearest zone that shares the same offset and daylight-saving rules.

Language and regional formatCopy Anchor Link

Below the timezone is a Locale field. It is read-only: it shows English (UK) and its hint reads Language and regional format. This is fixed to English (UK).. The display language and regional format are fixed to English (UK) and cannot be changed from this tab. You do not need to do anything with this field; it is shown so you can confirm the format Bulk applies.

Date/time previewCopy Anchor Link

The note below the fields shows the current date and time in the selected timezone, using English (UK) formatting. It helps you confirm which clock the organization uses.

Change the timezoneCopy Anchor Link

1. Open the Timezone selector and choose your organization's zone.
2. Bulk saves the selection immediately. There is no separate save button, and the selector is disabled while the update is pending.
3. Check the Date/time preview after the change. If the update fails, the selector returns to its previous value and Bulk shows an error.

Example: Wayne CorpCopy Anchor Link

Wayne Corp runs its Gotham Applied Sciences in the United Kingdom and coordinates the business from there. When the organization is first configured, an Owner sets a sensible default clock:

1. They open Settings › Organization › Settings and select the Localization tab.
2. In the Timezone selector they choose Europe/London, because the business is run from Gotham.
3. They glance at the Date/Time Preview, which now reads the current British time, and confirm it looks right.
4. They leave Locale as English (UK), since that is the supported format. The timezone selection has already saved automatically.

Later, Wayne Corp opens a second site in the United States. That new plant carries its own timezone (for example America/Chicago), set on the plant itself rather than here, the organization default stays Europe/London as the fall-back clock for the business as a whole.

Expected resultCopy Anchor Link

After you save, your organization's default timezone is stored and the Date/Time Preview reflects the zone you chose. The display language and regional format remain English (UK). The change is written to your organization's activity log, so there is a record of who set it and when. This organization timezone acts as a tenant-wide default, distinct from the timezone each individual plant carries.

Limitations and feature stateCopy Anchor Link

This feature is generally available. Keep these behaviours in mind:

• The display language is fixed. The Locale field is read-only and set to English (UK). You cannot change the language or regional format from this tab; only the timezone is editable.
• The timezone list is a curated common set. It does not include every IANA zone. If your exact city is missing, choose the nearest zone with the same offset and daylight-saving rules.
• Organization timezone is a default, not a per-plant override. Each plant carries its own timezone. This tab sets the organization-wide default and does not change any plant's own timezone.
• Timezone saves immediately. Review the zone before selecting it. An update requires Edit organization settings; rejected updates restore the previous selection.

TroubleshootingCopy Anchor Link

• The timezone returns to its previous value and an error appears. Check the reported error and your Edit organization settings permission. Ask an Owner to make the change if your role cannot edit it.
• Your city is not in the Timezone list. The selector offers common zones only. Pick the nearest zone that shares the same UTC offset and daylight-saving behaviour; the wall-clock time will match.
• A plant shows a different local time than the organization default. That is expected, plants use their own timezone. Confirm the plant was created with the correct timezone. Its timezone is fixed after creation. See Manage entities.

Related guidanceCopy Anchor Link

• Organization general settings, the neighbouring General tab, where you set your organization's name.
• Manage entities, the plants that each carry their own timezone.
• Working hours, the daily operating hours that sit alongside your localization defaults.
• Activity logs, review who changed localization, and when.