Administering › Managing Role Objects

Managing Role Objects

Role objects let you manage system permissions and privileges to define and simplify different access levels. For example, some users require view access to reports that are specific to their job titles. Other users must perform advanced searches and want to create subscriptions (groups of reports) for their teams. A different set of users wants to upload information to a repository. Also, your database and report administrators want extensive access and security permissions to manage the system and everyone who is using it.

The System Administrator or Group Administrator (GA) assigns all privileges and permissions to a role object, not to an individual. The Group Administrator can then assign all those individual users to the role as needed. This action creates a group of people who each have all the system access capabilities that are associated with that role.

CA OM Web Viewer includes only the Default User and System Administrator roles. You can define other role types manually. Although the other role types let you have more than one role object of a particular type, you can only have one System Admin.

Default User

If a user with valid mainframe credentials logs in to CA OM Web Viewer, but does not have access to any role, that user logs in using the Default User Role. Also, if the user has not been previously defined, that user has a user object defined automatically, and placed in the Default User Role. For more information, see Auto Enrollment - Mainframe Users.

The Default User Role can have repositories and privileges assigned to it in the same manner as any other role.

System Admin

The System Admin has complete access to the CA OM Web Viewer system. This role cannot bypass existing mainframe repository data restrictions in CA Dispatch, CA Deliver, or CA View.

All future Roles contain a subset of the System Admin privileges. The System Admin role is the only role in Web Viewer that can have a role type of System Administrator.

When you install CA OM Web Viewer, you must define a default system administrator. This Default System Administrator is the first member of the System Admin Role. You can add other users to the Role later to have more than one user with System Admin privileges.

Administrators design and maintain roles to control user permissions and their access to data, databases, repositories, and reports in the system. You can give an individual user more than one role assignment. For example, you have a Bank Teller role and you assign ten individual Bank Tellers, but you can assign the Bank Manager to a Bank Manager role, and also to the Bank Teller role.

This setup lets the Bank Managers operate with the privileges and data that the Bank Tellers use, but it also allows the manager to access a different set of data assigned to Bank Managers specifically.

Roles make the designation of privileges much less labor intensive:

• You can set or adjust the privileges for hundreds of users at one time by simply modifying the role.
• When the Group Administrator promotes or reassigns a user, they do not have to change privilege. They can simply assign that user to a different existing Role that has all the privileges necessary for the new job.
• You can assign an individual to more than one role.