Difference between revisions of "Block content access for administrative users"
(Created page with "__NOTOC__ ==Where to find it== * ''Manager'' > '''Administration > Server Settings''' menu > ''Security'' category > '''{{PAGENAME}}''' setting ==Purpose== This setting is se...") |
|||
| Line 4: | Line 4: | ||
==Purpose== | ==Purpose== | ||
| − | This setting is selected by default, and prevents users with the Administrator role from being able to create or change any content objects | + | This setting is selected by default, and prevents users with the Administrator role from being able to create or change any content objects. Specifically, if this option is selected, users with (only) the Administrator role assigned to them will only see the '''Administration''', '''Settings''', and '''Help''' menus in Manager. |
==Use== | ==Use== | ||
Latest revision as of 16:58, 13 May 2021
Where to find it
- Manager > Administration > Server Settings menu > Security category > Block content access for administrative users setting
Purpose
This setting is selected by default, and prevents users with the Administrator role from being able to create or change any content objects. Specifically, if this option is selected, users with (only) the Administrator role assigned to them will only see the Administration, Settings, and Help menus in Manager.
Use
This setting is useful for segregation of duty - especially where there many be several organizations using the same implementation, and a central Administrator overseeing all of them. If your Administrator is an Author (or, more likely, a Master Author), consider having separate Userids for both of these functions. The user will need to log off from one and on to the other to switch, but administrative tasks will likely be performed far less frequently, and this approach will ensure that content history logs always reflect the correct Author (and not "Admin" - which could conceivably be assigned to different people over time).
