|
22.
|
|
|
For a user to see any given part of your website, one of their usergroups needs<br />“{1} view access” for it, and for <span class="comcode_concept_inline" onmouseout="if (window.deactivateTooltip) deactivateTooltip(this,event);" onmousemove="if (window.activateTooltip) repositionTooltip(this,event);" onmouseover="if (window.activateTooltip) activateTooltip(this,event,'View access does not inherit. Instead, it works via a barrier system – there are certain barriers (shown in bold) that you need access through to get to a resource.','220px');">certain resources</span> above it in the Site Tree (marked by bold text).
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]PERMISSIONS_TREE_EDITOR_ABOUT_BARRIERS
|
|
42.
|
|
|
These restrictions allow you to define ad-hoc match-keys to restrict page access on a parameter level; for example, you could allow viewing, but not adding, of downloads. Specified details provide extra restrictions, not permissions. If you need more input fields, click ‘Proceed’ and more will be available on return to this screen.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]PAGE_MATCH_KEY_ACCESS_TEXT
|
|
133.
|
|
|
Please note that there is only one overridable permission available here, and therefore the preset you have chosen is unlikely to be representive.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]JUST_PRESETS
|
|
136.
|
|
|
Click on some blank space in a permission row below to copy permissions to that row. Repeat clicking permission rows as required. Click the button again to stop the process.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]REPEAT_PERMISSION_NOTICE
|