The function of the assignments pane is to permit the display and manipulation of object assignments and other configuration settings for the owner currently selected in the owners tree.
As a user navigates the owners tree, the assignments pane will be reloaded with assignment/configuration data for the newly selected owner.
All changes made to an owners assignments or configuration data occur within the assignments pane. The only exception is when objects/groups are manipulated in the objects pane (i.e. deleted, enabled/disabled, objects moved into/out of groups).
The assignments pane is composed of an assignments toolbar and an assignments tree. The organization of the assignments tree is very similar to that of the objects tree. Object assignments are made with a drag-and-drop operation from the objects tree to the corresponding section in the assignments tree.
The name of the selected owner will appear in the title bar of the assignments pane. The owner is also represented by the highest level branch in the tree.
Controls in the assignments toolbar will dynamically change as a different row is selected. The assignments tree only permits single selection at this time.
Direct assignments are made by a drag-and-drop operation from the objects tree into the assignments tree. The currently selected owner is the recipient of a direct assignment.
Only direct assignments may be deleted.
All descendants of an owner to which a direct assignment indirectly acquire it. This is referred to as an inherited assignment.
Inherited assignments may not be deleted.
It’s possible to designate that certain sets of assignments be blocked or ignored for a particular owner and its descendants. To block any or all of inherited, direct, server, or client assignments for an owner, select the top (owner’s) row in the assignments tree. Four toggle icons will appear in the assignments toolbar. Click an icon to block that set of assignments – click again to allow them.
Any assignment (direct or inherited) may be denied for an particular owner. The denied state of an assignment is also inherited, i.e. if an owner is denied an assignment, all descendants of that owner will be denied the assignment.
An assignment (permitted or denied) may be overridden at the descendant level, i.e. if an assignment is permitted or denied at the ancestor level, the state may be reversed for any particular descendant. This is accomplished by selecting the descendant owner in the owners tree, finding the assignment in the assignments tree, and clicking the appropriate assignments toolbar button (permit/deny).
If the Simplify Lockdown component has been licensed, an owner’s lockdown mode may be directly set by selecting the Lockdown row in the assignments tree – then selecting the desired mode in the combobox in the assignments toolbar.
Lockdown mode may be inherited and overridden just as object assignments are.
If the Simplify Desktop component has been licensed, an owner’s shell (Explorer or triShell <link>) may be directly set by selecting the Shell row in the assignments tree – then selecting the desired shell in the combobox in the assignments toolbar.
An owner’s Shell may be inherited and overridden.
If the Simplify Printing component has been licensed, a user may have one or more types of printers assigned (e.g. ScrewDrivers, Print Server, network, local, etc.). One (at most) of the assigned printers (regardless of type) may designated the owner’s default printer. Select the desired printer and click on the Set/Clear As Default Printer icon in the assignments toolbar.
The default status of a printer may be inherited and overridden.
A denied printer assignment may not be set as the default printer.