Multilingual teams

One workspace. Every language your team speaks.

Your team isn't all in one language — so your project tool shouldn't force them to be. Artala lets each person work in their own language, script, and calendar, on the same data, at the same time.

Plenty of teams are multilingual by default: a manager in Dubai, developers in Lahore, a client contact in London. Today they usually compromise — everyone squeezes into English, or the tool half-translates and the right-to-left users fight broken layouts, or work splinters across WhatsApp and spreadsheets because no single tool fits everyone. Artala is built so one shared workspace serves all of them, each in their own way.

The same data, in each person's language

Language in Artala is a per-user preference, not a workspace-wide setting. The interface, menus, buttons, and email notifications all appear in each person's chosen language — 32 of them — while the actual content (task titles, comments, descriptions) stays exactly as it was written. No one is forced into someone else's language to use the same boards.

Both directions, at the same time

This is the part a "supports 32 languages" checkbox doesn't deliver. When an Arabic or Urdu reader and an English reader open the same task and comment thread, the shared text renders correctly for each of them — right-to-left for one, left-to-right for the other — at the same time, on identical data.

Artala does this by reading a line's base direction from the content's own script rather than its first character, so mixed text (Arabic with an English brand name, Urdu with an SKU or "POS") doesn't scramble: punctuation and Latin tokens stay where they belong, and nothing flips when a teammate switches the interface to another language. It reads the same whether you're viewing or editing.

Most tools were built English-first and translated later — the words change but the layout doesn't truly mirror, and mixed text breaks. Artala was built for right-to-left and 32 languages from the ground up, which is why the same workspace can be genuinely bidirectional instead of bilingual on paper.

Each person's calendar and working week

Dates work the same way. A user in Riyadh can see the Hijri calendar (Umm al-Qura), a user in Karachi can adjust it to local moon-sighting, and a user in London stays on Gregorian — all looking at the same deadlines. Working weeks are configurable too (Friday/Saturday, Thursday/Friday, or whatever your region keeps), so the calendar and timesheets shade the right non-working days for each region.

Notifications in the recipient's language

Localisation doesn't stop at the screen. Email — invitations, due-date reminders, the weekly digest with its AI-written summary — goes out in each recipient's own language, right-to-left where it should be. The teammate who mostly lives in their inbox still gets a native experience.

How it works — nothing to configure

See one workspace in two languages

Two ready-made demos, no signup: مؤسسة الواحة التجارية (a Saudi retailer in fully mirrored Arabic with the Umm al-Qura calendar) and فریسن ٹریڈرز (a Pakistani trading company in Urdu with an adjustable Hijri calendar). Open a board in each and switch your interface language — the content holds its direction either way.