002. Localizer access control

Be sure to give necessary Localizer privileges to appropriate roles under Administer > User management. The most important one is to make sure you enable "Localizer content: access translations" for every role (including anonymous) you want to be able to view translated content. If you do not enable this, your visitors will get "page not found" errors when trying to access translated nodes.

When the privileges "Localizer content: administer translations" and "Localizer strings: administer translations" are enabled, access to the Localizer strings translation and Localizer content translation administration interfaces under Administer › Content management is granted.

When the privilege for "Localizer content: create translations" is enabled, translations can be created.

When the privilege for "Localizer content: disconnect translations" is enabled, translations can be "disconnected" from other content, or in other words, the link that identifies it as a translation of some other node(s) can be broken.

When the privilege for "Localizer content: view all available" is enabled, all nodes, regardless of creator, are available to be linked as translations.

When the privilege for "Localizer content: view own available" is enabled, only nodes created by that specific user are available to be linked as a translation. Or, to state it backwards for clarity, nodes created by other users are not available to be linked as a translation.

When the privilege for "Localizer content: delete translations" is enabled, translations can be deleted.

The language-specific "Localizer translation management:" options allow you to restrict the ability to create, edit, and disconnect translations to specific languages. This is useful if you want to set up roles that can manage only specific languages such as for a translator who will only work with Italian, or another translator who will only work with Japanese, etc.