Skip to content
Getting started

Language, dates and theme

Two languages, the Jalali calendar, and why figures stay in Latin digits.

Last updated 2 min read

Language belongs to the user, not the workspace

Each person picks their own, and their choice affects nobody else. Half a team can work in Persian and half in English while looking at the same data.

Choosing Persian flips the whole layout right-to-left, not only the text. In the language picker every language is written in its own script, because a list where every option is in one language is a translation somebody forgot.

Dates and numbers

These two deliberately behave differently.

PersianEnglish
DatesJalali, with Persian digitsGregorian, following the browser locale
Numbers and amountsLatin digits, thousands groupedLatin digits, thousands grouped
Text directionRight to leftLeft to right

Why amounts are never converted to Persian digits

Financial figures stay in Latin digits even on a fully Persian page. The reason is that these figures get copied — into a spreadsheet, into an email, into a tax filing — and a Persian digit is not a number in those destinations, it is text.

Dates are the opposite: a date is read rather than copied, so in Persian it is written in the Jalali calendar with Persian digits.

Light and dark

The theme has three states: light, dark, and "match the system". The default is the third and stores nothing; the moment you make an explicit choice it persists, until you go back to the system setting yourself.

Like language, this setting belongs to your account rather than to the workspace.

Common questions

  • Can I force Persian for the whole team?
    No. Language is each user's choice. Forcing it in a bilingual team reliably produces people who stop using the tool.
  • Can I see Gregorian dates while the interface is Persian?
    No. The calendar follows the language; there is no separate setting.

Still stuck?

If the answer wasn't here, write to us. It is a real inbox and it gets answered.

Talk to us