|
|
1.
|
|
|
The permissions tree editor allows you to see and set permissions for all site structure and content from a single user-friendly interface. It is designed to allow quick setting of permissions without having to crawl through a different screen for everything being worked with.
|
|
|
|
|
L'éditeur de l'arbre des permissions vous permet, d'une seule interface conviviale, de voire et de fixer les permissions pour toute la structure et contenu du site. Il a été conçu pour attribuer rapidement les autorisations sans avoir à traverser de multiples écrans pour chaque élément ciblé.
|
|
Translated and reviewed by
Gary Andrews
|
|
|
|
Located in
[strings]DOC_PERMISSIONS_TREE
|
|
|
2.
|
|
|
Specific-permissions -- rather than controlling access permissions, control whether somebody is allowed to do something more specific, such as use high-level Comcode, or bypass the word-filter. Think of them as 'privileges'.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DOC_SPECIFIC_PERMISSIONS
|
|
|
3.
|
|
|
If it is not enough to specify whether a member can access a specific page based on the available view permissions and overridden specific-permissions, you can also set things up to deny access to pages based on the URL parameters they are opened with. This could be used, for example, to allow members to browse through download categories but not actually view any download entry.\nThe match-key permission system is not intended to be used unless really needed - it is there to provide additional control when page and specific-permissions won't meet your unique needs.\n\nTo add a new match-key permission, go to the "Match-key page restriction" icon in the Security section of the Admin Zone.\n\nAn example match-key that would deny access for viewing download entries would be: [tt]_WILD:downloads:type=view[/tt]. Usergroups could be ticked (checked) to deny member's in those usergroups access to the website screen that actually views a download ([tt]type=entry[/tt] is that interface).\n\nAt the bottom of the same screen you can choose what error message to display if someone is denied access. This is very useful if you have a specific reason for closing down access to something that you wish to explain.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DOC_PAGE_MATCH_KEY_ACCESS
|
|
|
4.
|
|
|
“{1}” does not have access to re-use this attachment.
|
|
|
|
|
“{1}” n'a pas le droit de réutiliser cette pièce jointe.
|
|
Translated and reviewed by
Gary Andrews
|
|
|
|
Located in
[strings]ACCESS_DENIED__REUSE_ATTACHMENT
|
|
|
5.
|
|
|
“{1}” does not have the specific-permission, ‘{2}’.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]ACCESS_DENIED__SPECIFIC_PERMISSION
|
|
|
6.
|
|
|
“{1}” does not have access to this category.
|
|
|
|
|
“{1}” n'a pas accès à cette catégorie.
|
|
Translated and reviewed by
Gary Andrews
|
|
|
|
Located in
[strings]ACCESS_DENIED__CATEGORY_ACCESS
|
|
|
7.
|
|
|
“{1}” does not have a sufficient access level for this category.
|
|
|
|
|
“{1}” n'a pas un niveau d'accès suffisant pour cette catégorie.
|
|
Translated and reviewed by
Gary Andrews
|
|
|
|
Located in
[strings]ACCESS_DENIED__CATEGORY_ACCESS_LEVEL
|
|
|
8.
|
|
|
“{1}” does not have access to this page.
|
|
|
|
|
“{1}” n'a pas accès à cette page.
|
|
Translated and reviewed by
Gary Andrews
|
|
|
|
Located in
[strings]ACCESS_DENIED__PAGE_ACCESS
|
|
|
9.
|
|
|
“{1}” does not have access to anywhere this attachment is displayed.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]ACCESS_DENIED__ATTACHMENT_ACCESS
|
|
|
10.
|
|
|
“{1}” does not have access to this catalogue.
|
|
|
|
|
“{1}” n'a pas accès à ce catalogue.
|
|
Translated and reviewed by
Jean-Paul GERST
|
|
|
|
Located in
[strings]ACCESS_DENIED__CATALOGUE_ACCESS
|
