Administering CA Output Management Web Viewer › Repository Object › Filter Options Concepts › Using Owner Roles with Repositories - Overview

Using Owner Roles with Repositories - Overview

Owner Roles refer to any Roles that are allowed to access this Repository. There may be situations where only certain Repositories need to be available to a Role.

Depending on how your reports are divided between your Repositories, it might make sense to only allow a certain Role to access certain Repositories. For example, if all your sales Reports are in a certain Repository, the Salesman Role would be allowed access to that Repository. Additionally, the Salesman Role might not be allowed to access a Repository with accounting information stored in it. A Repository maps to exactly one CA View, CA Dispatch, or CA Bundl system.

Just because a Role has access to a Repository, does not necessarily mean every user in that Role will be able view every Report in that Repository. Limiting a Role’s access to Repositories is one of several ways of limiting access to reports in CA OM Web Viewer and the base Repository systems.

In order for a user to see report information, their mainframe account or proxy profile must have access to the report in the base one CA View, CA Dispatch, or CA Bundl system.

Report access can be further limited within the mainframe repositories. Be aware that Users cannot access reports that they are not allowed to access through the mainframe system. One work-around for this is to set up a Profile account. See the Profiles section for more information.

For example: If Advanced Users, Group Administrators, and System Administrators have a Repository object assigned to their Role, they can view any report in that Repository object’s base system that their mainframe credentials would normally have access to in the base one CA View, CA Dispatch, or CA Bundl system.

Be aware of the following additional factors:

• Report access can be further limited with Subscriptions in CA OM Web Viewer. Basic User Roles only allow their users to access reports assigned to the Role with the subscriptions they are to be able to view. (See Role - Assigning Subscriptions to a Role)

  However, to view a report, even if the report has been assigned with a subscription to the user’s Role, that user’s Role has to have access to the Repository where the report resides, to view the Report. Basically, both have to be true; the report must be assigning in a subscription to the Role, and the Repository the report is in must also assigned to a user. (See Subscription – TODO exact place)

• Roles can also be given access to a Repository at the Roles panel. (See Assigning Repositories to a Role) However, the System Administrator Role cannot be edited from the Role panel; so to add the Systems Administrator Role to a Repository it must be added from this panel.