Interface language for contact with access to Planfix

From Planfix
Revision as of 12:03, 14 December 2023 by Dmitri (talk | contribs) (Created page with "{{#seo: |title=Interface language for a contact with access to Planfix |titlemode=append |keywords=planfix, contacts, language, interface |description=Interface language for a contact with access to Planfix }} Setting the language for an external contact with access to Planfix affects: *The language of system notifications he receives *The language in Personal Account, which is automatically available to all co...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Setting the language for an external contact with access to Planfix affects:

Setting the interface language for contact with access to Planfix

When creating a contact, select the desired interface language in their card:

ZiT69h.jpg

Then, they will immediately receive an invitation to the system in the selected language.

You can also change the interface language while editing the contact card. From the moment the new value is saved, the contact will start receiving notifications and see the system interface in the selected language (if there are templates for notifications in this language in the system).

Important features

Since Planfix has extensive customization capabilities, there are some features of its use in multilingual mode that you need to consider, ensuring the comfortable work of customers in your account. These features are related to the fact that changing the language leads to the display in the selected language of the interface itself, but not the content added to the system.


Obvious example: If you create a task with a Russian theme and Russian description and then connect an English-speaking client to it, they will see it in an English interface, but the theme and description of the task will remain Russian.

Less obvious example: if you created an "Overdue tasks" filter and gave access to it to an external contact with access to Planfix, then your English-speaking contact will see the Russian name of this filter that you came up with in their filter list and may be confused by this.

Conclusion: When working in an account with users with different interface languages, it makes sense to agree on a single language in which common use objects will be named or not to give access to them to users who do not understand your main language.


The list below will make it easier for you to find key places where content in a language unfamiliar to the user may be encountered:

  • Planfix section!:
    • All tasks to which the contact has access.
  • Planner:
    • Standard planners are created for the user in the language set in their card at its creation.
    • Additional planners (the name of the planner itself, the names of lists inside the planner) to which the contact has access.
  • Projects:
    • The name, description, and custom fields of projects to which the contact has access.
  • Tasks:
    • Names of filters created by other users and available to this contact.
    • System filters for custom task statuses if no language alternatives are specified. In the settings of each custom status, there is an opportunity to specify its name in all supported languages.
    • The name, description, and custom fields of tasks to which the contact has access.
  • Documents:
    • The name and description of documents to which the contact has access.
  • Reports:
    • Names of reports to which the contact has access.
    • Headers of columns and rows of totals in such reports.
  • Contacts:
    • Names of additional filters created by other users to which the contact has access.
    • Contact names/company names and data about them.

Advice

  • Add a test contact with access to Planfix in the required language with an e-mail address you have access to
  • Log in under their account and look at the system through their eyes
  • Make the necessary changes to the names of objects and/or access rights to them so that users with the selected language don't experience inconvenience from the presence of an unknown language in Planfix.


Go To