Document user permission

This commit is contained in:
Ingo Schommer 2015-04-27 13:59:42 +12:00
parent 10a8352a6b
commit 94945a49cd

View File

@ -128,6 +128,37 @@ See http://www.w3.org/International/articles/language-tags/ for a detailed descr
To ensure that your template declares the correct content language, please see [i18n](i18n#declaring_the_content_language_in_html). To ensure that your template declares the correct content language, please see [i18n](i18n#declaring_the_content_language_in_html).
### User Permissions
Permissions to view and create translations are managed through the CMS, based on security groups
defined in the "Security" section (`admin/security`). By default, all CMS users with rights to create and edit pages
can also create translations. This can be restricted by removing the "Translate into all available languages" permission,
and replacing it with language specific permissions.
You can further restrict viewing and editing rights on a specific language through the "Settings" section (`admin/settings`).
Each language has its own configuration "translation", and you can configure access to groups there.
Here's an example setup which allows content authors to write only English master content,
while translators can only write German translations, but still see readonly versions of the English master content.
Group: Administrator
* Has "Full administrative rights" permission
Group: Content Author English
* Has "View language dropdown" permission
* Has "Translate into English" permission
* Is part of "Who can edit pages?" in "Settings" for "English"
* Is part of "Who can create pages?" in "Settings" for "English"
Group: Translator German
* Has "View language dropdown" permission
* Has "Translate into German" permission
* Is part of "Who can edit pages?" in "Settings" for "German"
* Is part of "Who can create pages?" in "Settings" for "German"
### Usage ### Usage
Getting a translation for an existing instance: Getting a translation for an existing instance: