Browsing Spanish translation

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'.

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.

4.

“{1}” does not have access to re-use this attachment.

5.

“{1}” does not have the specific-permission, ‘{2}’.

6.

“{1}” does not have access to this category.

7.

“{1}” does not have access to this page.

8.

“{1}” does not have access to anywhere this attachment is displayed.

9.

“{1}” does not have access to this catalogue.

10.

&ldquo;{1}&rdquo; does not have access to the zone <tt>{2}</tt>.

11.

Your login as &ldquo;{1}&rdquo; must be confirmed before you may enter this high-security area (you do not currently have a confirmed session).