Localization displays the SV3 Enterprise web application and Kiosk in a language other than English. Learn which settings administrators translate and what visitors see.
What visitors see
At the Kiosk, a visitor selects the language they want to use. For each piece of text, the Kiosk shows the translated version your admins entered for that language. If no translated version exists, the Kiosk shows the English version.
This means you can translate as much or as little as you need. A Visit Type name in Spanish can sit next to a destination name that only exists in English.
What you can translate, and who can do it
- Documents: the documents visitors sign at check-in. Global Admins only.
- Visit Types: the Visit Type name and its sign-in field labels. Global Admins and Local Admins.
- Custom fields: the question, the answer choices, and the answers that put a visitor on Pending Approval. Global Admins and Local Admins.
- Destinations: the destination name and notes. Global Admins and Local Admins.
- Your Dashboard language: any user can change the language the Dashboard displays in. This setting affects only your own view.
Where each setting applies
Documents are account-wide. Translate a document once, and every Location that uses it shows the translation.
Visit Types, custom fields, and destinations are set per Location. Translating one of them at one Location doesn't change it at any other Location, even if another Location has one with the same name. If several Locations share a Visit Type name, translate it at each Location.
A Local Admin can translate Visit Types, custom fields, and destinations only at the Locations they're assigned to.
How translation works in each form
Every form that supports translation has a language list next to the text it controls, set to English (United States) by default. Select a language, then enter the text as it should read in that language. English stays as it is.
A translated custom field needs every part entered again for that language, including its answer choices. Custom fields are translated on the Custom Fields tab, not with the Visit Type's sign-in fields.
Comments
0 comments
Article is closed for comments.