Visara Master Console Center Administration Guide - Manual (Page 125)

Chapter 8 Administering Users
Administration Guide 125
Setting Security for Consoles
By default, members of a security group do not have access to a console. The
group permissions must be changed to VIEW (read-only access) or UPDATE
(read/write access) to allow access to the console. Changes only take effect when
a user logs out and back in again.
Console for CPU:OS combination:
If a console is defined in both CPU and OS sections of the system.cfg file (see
Chapter 5 MCC system.cfg Configuration File), the cpu and os selections must
be set to Update for members of the security group to have full access to the
console.
Note: Defining both a CPU and an OS for a console is a typical
configuration. It allows the console to be referenced by GCL
scripts, and permits a Console History Log to be generated.
Console for CPU:
If a console is defined in the CPU section of the system.cfg file and not in the OS
section, the cpu selection must be set to Update for members of the security
group to have full access to the console.
Note: If no OS is defined on a CPU, the os selection and drop-down list
are not shown.
Standalone Console:
If a console is not associated with a CPU or an OS, setting the Other selection to
Update allows members of the security group full access to the console.
Console with VIEW Permissions:
A console with VIEW permissions set contains a “View Only” status indication in
the status bar at the bottom of the console window. A console of this type
behaves like a printer console.
Note: A Command Console with VIEW permissions behaves as if
UPDATE permissions are set. The user has full read and write
access to the console.