Content Translation is available as a beta feature. In many cases, it is enabled explicitly by the user from the beta feature page. However, there are some cases, where the beta feature is enabled automatically, and we want to make sure these don't generate any conflict with Global preferences (MediaWiki-extensions-GlobalPreferences).

The cases where Content Translated can be enabled programmatically are:

• From an invite. When creating a new article, Content Translation si suggested as a way to create it by translating. If users accepts the invite, they navigate to Content Translation and the beta feature gets enabled automatically.
• From a link. In order to support translation campaigns, it was possible to prepare a link for an article to be translated with Content Translation, clicking on it enabled the beta feature for the user automatically in case they had not done it before on the target wiki.
• Switching languages. Similarly, given that you can only write content of a wiki from that wiki, Content Translation switches to a different wiki as you select a different target language. As a result, the user can access the tool even if it was not explicitly enabled in such wiki to facilitate navigation. For example, a user enabling Content Translation on English Wikipedia can select Spanish as a target language, which would result in a navigation to Spanish Wikipedia version of Content Translation.

As part of this task we want to:

• Verify the above list is complete.
• Evaluate whether the above scenarios create any conflict with Global preferences.
• Decide whether to solve the identified conflicts by creating local overrides or changing the global value for the preference in the above cases. This also depends on the APIs available.