Manage - Auto-Translated User or Location Names

Manage - Auto-Translated User or Location Names

Brief Description

Some users may experience Select Usernames or Clinic/Location names being automatically translated or altered within the Appointments and Scheduler views. This may result in staff or clinic names displaying as translated words instead of their original values.

This issue has been identified in a small number of accounts and is typically caused by browser page translation features or translation plugins.

Decision Steps

1. Verify the Issue

Ask the user:

  • Are names appearing translated or changed only in specific screens such as Appointments or Scheduler?

  • Are other users in the same clinic experiencing the same issue?

  • Is a browser translation plugin or automatic page translation feature enabled?

Validation:

  • Confirm only specific names are affected

  • Confirm the issue is isolated to individual user accounts and not system-wide

2. Check Browser Translation Settings

Ask the user to disable any browser translation features or extensions.

Google Chrome

  • Translation icon in address bar

  • Settings → Languages → Google Translate

  • Chrome Menu → Extensions → Manage Extensions

Microsoft Edge

  • Settings → Languages → Offer to translate pages

  • Check installed extensions

Firefox

  • Menu → Add-ons and Themes → Extensions

  • Disable translation-related add-ons

After disabling translation tools, refresh the page and retest.

Outcome:

  • If names display correctly, the issue is resolved

  • If not, proceed to next step

3. Reset Language Settings in Manage

  • Go to: Settings → My Profile → Settings → Language

  • Select or reselect the correct language (e.g., English)

  • Save changes

  • Log out of Manage

  • Log back in

Validation:

  • Confirm translated names no longer appear

  • Confirm correct display in Appointments and Scheduler views

Final Resolution Step

Disable browser translation features or reset the system language settings in Manage, then log out and log back in to apply changes.

Required Information for Escalation

If the issue persists, collect:

  • Affected user account names

  • Screenshots of incorrect translations

  • Browser type and version

  • List of installed browser extensions

  • Confirmation of browser translation status

  • Examples of incorrectly translated names

  • Confirmation that logout/login was completed after changes

If Issue Persists

If the issue continues after completing all troubleshooting steps, contact:
support@auditdata.com

Additional Notes

  • This issue is not caused by data corruption in Manage

  • It is typically related to browser translation tools or extensions

  • Logging out and back in is required after language changes to apply updates

    • Related Articles

    • Manage Permissions Catalog

      Who this is for: Administrators who need to understand what a permission does, why a user can't do something, or what permissions to assign to a new role. In Manage, administrators configure roles under Company Settings → Roles. A role is simply a ...

    • Location settings

      When configuring location settings, note that: Each AREA can contain one or multiple REGIONS Each REGION can contain one or multiple LOCATIONS Each LOCATION can be associated with a single BRAND By adhering to these guidelines, you can effectively ...

    • Regions - Location Groupings

      A region is a group of locations.  There are various types of Regions, as displayed next in the excerpt from the HELP manual. From the list of menus on the left of your screen, at the bottom of the screen look for HELP. Click it, then click ...

    • Bridge 2.X. Getting Started Guide

      Learn how to: Use Bridge Online Mode Configure User Settings Review Client Data Delete Audiometry Session Actions Work with Measurement Modules Manage Journal Records Export NHAX Client Data Import NHAX Client Data Use Bridge Offline Mode Use ...

    • Bridge - "Error: Cannot validate NOAH User"

      Issue: Error message: "Cannot validate Noah User" Root Cause: The Noah clientsettings.xml configuration file is not valid. The server name in this file is not set to “localhost”. As a result, Noah will attempt to connect to a Noah network server if ...