White Papers

Scope Based Access Control with OpenManage Enterprise 3.6|Document ID: 21396 P a g e | 11
The user will see the hierarchy from “All Devices”
to the groups that have been granted to the
Device Manager.
The Device Manager will not see the hierarchy
from “All Devices” to other built-in / custom /
plugin groups, to which access has not been
granted.
Configuration: Firmware
(FW) / Driver compliance:
Catalog Management
No changes.
FW Catalogs are treated as community entities.
Configuration: FW / Driver
compliance: Baselines
Yes.
Device Managers can see only the baselines that
they own.
Target Picker only shows FW update capable
devices / groups that are in the Device
Manager’s scope.
Configuration: FW / Driver
compliance: Compliance
Report
No changes.
Given a set of targets, the update should only run
for those targets that are in the Device
Manager’s scope. The targets are evaluated for
scope when the update job runs.
Configuration: Templates
Yes.
Device Managers can see only the built-in
templates and templates that they own.
Only “Clone” and “Export” are allowed on built-in
templates. The target picker only shows “Deploy
capable” devices / groups that are in the Device
Manager’s scope.
Configuration: Profiles
Yes.
Device Managers can see only the profiles that
they own.
Target Picker only shows “Deploy capable”
devices that are in the Device Manager’s scope.