Some knowledge base owners want to influence how third-party browser translation tools behave on their site, but currently have no way to inspect or adjust page-level translation-hint markup (such as an attribute that signals "do not translate," or a notranslate-style meta tag) from within the portal.

Suggested Enhancement: Provide a portal setting to view and control translation-hint markup and tags on published pages, so knowledge base owners can decide whether browser-based translation is offered to readers alongside native localization.

Customer Benefit: Knowledge base owners could support readers who rely on their browser's built-in translation, in addition to Document360's native localization, without needing custom development work.