---
title: "Employee Screen Languages Without Changing the Tenant…"
description: "How a worker's preferred Workday language can drive a screen without changing the tenant default for every locale."
url: https://kiweely.com/guides/localization-beyond-one-language-without-tenant-default
---

# Employee Screen Languages Without Changing the Tenant Default

Workday picks a display language from the user, then the locale, then the location, then the tenant. Enabling a language can change the default for every user in the related locales. A screen should follow the worker’s preferred language instead.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   3 min read
-   Published November 16
-   By Kiweely

A warehouse may need Spanish, Vietnamese, and Polish on the phone while the Workday tenant stays in English for everyone else. Those are different switches. Workday’s language enablement changes defaults for whole locales. A pass-through screen can follow one worker’s preferred language without that tenant-wide change, and it should use Workday’s translated values when they exist.

[Kiweely Leaf](https://kiweely.com/leaf) (coming next) says screens use your languages and Workday’s own words. It does not flip **Edit Tenant Setup - Global** for you.

## How Workday chooses a language

[Workday describes three layers](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/globalization/global-tenant-setup/vec1511195045421.html). Locales format dates, times, and numbers. Languages control text. Localized fields hold country-specific data such as names and addresses. To pick the display language, Workday evaluates, in order: the user’s selected language, the user’s selected locale, the selected language of the user’s location, the selected locale of that location, the tenant’s selected language, and the tenant’s selected locale. The documented default locale is US English.

Workers at a business site inherit that site’s locale when you set it on the location. If you do not, the location inherits the tenant default locale.

[Edit Tenant Setup - Global](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/dan1370796747763.html) lists each language and whether it is Workday-supported. Selecting **Enabled** makes that language the default display language for users in the associated locales, and it lets users pick it as a preferred display language override. Workday’s sentence is the one to remember: when you enable a new Workday-supported language, users in the associated locales see that language instead of English until they open **Change Preferences** and set **Preferred Display Language** back to English. Enabling a language so a screen can offer it is not a private change. It moves the default for those locales.

Workday does not deliver interface translations for languages it does not support. You can still enable them and translate tenanted data, which helps integrations. It does not translate Workday’s own UI.

[Manage Translations](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/globalization/languages-and-translations/dan1370797879452.html) is where your plan names, absence types, and other tenanted text get a translation. If a field has no translation, Workday saves edits in the base language. On employee and manager self-service, with **Allow Mixed-Language Transactions** clear, only items translated into the preferred language display. Turn the screen on in Polish before the absence types are translated, and self-service can come back blank. Mixed-language on the account lets the worker see English for what you have not translated. That is a Workday account setting, not a CSS fallback.

Users apply a preferred language by setting **Preferred Display Language** and signing in again. The tenant default language itself is **Preferred Display Language** under **Edit Tenant Setup - System**.

## What the screen should do

Read the signed-in worker’s preferred display language and format dates and numbers for their locale. Use the descriptors Workday returns in that session, which are already in the language Workday selected. Where you add your own sentences, translate those strings in the layout for the languages you support. Do not enable a tenant language merely to unlock a phone screen. If the language is already enabled, workers can set the preference themselves, and the screen follows the session.

| Goal | Action |
| --- | --- |
| One worker reads the phone in Vietnamese | Their Preferred Display Language, after Vietnamese is already a language your tenant meant to enable |
| Avoid switching every worker in those locales | Do not enable the language only for the screen. Enabling it changes the locale default. |
| Plan names appear in that language | Translate the business object. Untranslated self-service fields can disappear when mixed-language is off. |
| Dates look local | The worker’s locale, which is separate from language |
| Everyone’s Workday UI moves | Edit Tenant Setup - Global or the tenant Preferred Display Language. That is an administrator decision, not a screen publish. |

[Leaf](https://kiweely.com/leaf) (coming next) can ship the phone layout in the languages you name. Workday remains the source of the plan names and the user preference. Tell us which languages the first screen must support, and whether those languages are already enabled.

## Questions

### Will the screen translate Workday for us?

It can show the words Workday already returns for that user’s session, and your own captions in the languages you provide. It does not create Workday-supported UI translations for a language Workday does not ship.

### Is locale the same as language?

No. Locale formats dates and numbers. Language selects text. A worker can need UK date order and English text, or US date order and Spanish text. Set them as Workday does, as two preferences.

## Sources checked

-   [Concept: Country-Specific Information, Locales, and Languages](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/globalization/global-tenant-setup/vec1511195045421.html)
-   [Reference: Edit Tenant Setup - Global](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/dan1370796747763.html)
-   [Steps: Set Up Country-Specific Information, Locales, and Languages](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/globalization/global-tenant-setup/phd1511257946785.html)
-   [Steps: Manage Translations](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/globalization/languages-and-translations/dan1370797879452.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Publishing One Employee Screen to Web, Teams, and Phone Leaf publishes one screen into the browser, workplace chat, and the Leaf phone app. Workday Everywhere is Workday’s own conversational app in Teams, Slack, Copilot, and Gemini Enterprise. They answer different problems and do not replace each other.](https://kiweely.com/guides/one-screen-definition-web-teams-phone)

### More guides on Tenants and developer accounts

[All 25 guides](https://kiweely.com/guides#tenants)

-   [Accessing Employee Payslip Summaries and PDF Payslips Through Workday APIs](https://kiweely.com/guides/workday-payroll-payslip-summary-pdf-retrieval-apis)
-   [How Workday Stores Custom Plan Names, Reason Codes, and Translated Labels Across APIs](https://kiweely.com/guides/workday-custom-labels-translations-reading-tenant-terminology)
-   [Why Workday W-2 Box 1, 3, or 5 Wages Don’t Match Payroll Summary (and How to Fix Them)](https://kiweely.com/guides/workday-w2-box-mismatch-adjust-tax-balances)
-   [How to Customize the Workday Home Page, Daily Brief, and Global Navigation Sidebar](https://kiweely.com/guides/workday-configurable-home-page-daily-brief-setup)
-   [Workday Payroll Parallel Testing and Retro Calculation Audits in Sandbox](https://kiweely.com/guides/workday-payroll-parallel-testing-retro-audit)
-   [Workday Test Data: How to Build Realistic Data in a Sandbox or Implementation Tenant](https://kiweely.com/guides/workday-test-data-sandbox)
-   [How do I plan end-to-end and regression testing in Workday, and what does a test scenario cover?](https://kiweely.com/guides/workday-end-to-end-testing)
-   [How to get a Workday developer account and a free development tenant](https://kiweely.com/guides/workday-open-developer-program-getting-started)

### From the blog on Tenants and developer accounts

[All posts](https://kiweely.com/blog)

-   [Designing Three-Button Workday Screens for Warehouse, Retail, and Healthcare Workers](https://kiweely.com/blog/simplifying-workday-for-frontline-warehouse-retail-healthcare)
-   [How to Test a Workday MCP Connector in Claude or ChatGPT Using a Free Developer Tenant](https://kiweely.com/blog/testing-workday-mcp-connectors-on-free-developer-tenant)
-   [Running AI Across a Workday Consulting Practice Without Mixing Client Tenants, SOWs, or Token Budgets](https://kiweely.com/blog/how-boutique-workday-firms-manage-shared-ai-seats-and-client-boundaries)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
