Locking specific language versions in Table View

How: Introduce the ability to lock a specific language version of a field in Table View. Instead of locking the entire field for all languages, a user should be able to pin one localization (such as English) so it remains visible as a reference while the user continues editing the same field in their own local language.

Why: single language version, it is easy to unintentionally overwrite the reference language while switching between fields. Allowing language-level locking ensures smoother editing, prevents accidental changes to the master language, and makes comparison between languages clearer and safer.

For Who: Everyone who regularly work with multilingual product information in table view and need to reference one language while editing another, including content reviewers, translators, product information managers and so on.

Impact: Reduce the risk of inconsistent or unintentionally altered product information, and minimize the need to switch between different views. Overall, it would create a more efficient, accurate, and user‑friendly experience when working with localized content in Table View.

Additional context: Many organizations use English as their master language, and users frequently need to keep that version visible and protected while producing localized descriptions. This functionality supports a common multilingual workflow in table view and ensures the master language remains intact during editing.

Please, add your suggestion and feedback above to add to the insights used by Product team when deciding priorities and direction of the Inriver PIM.