How to Hide the Catalog UI from the Global Header in Oracle Analytics Cloud Service (OACS)

Background

This blog was originally published on Feb 3, 2014 for Oracle Business Intelligence Enterprise Edition (OBIEE). It was updated on Jan 23rd, 2019 for Oracle Analytics Cloud Service (OACS). The steps are still applicable to Oracle Business Intelligence Cloud Service (BICS) and Oracle Business Intelligence Enterprise Edition (OBIEE).

By default all users with the BI Consumer role can view and run any analyses, dashboards, and agents directly though the Catalog UI. This article discusses why that may be undesirable and the steps required to alter the default setting to hide the Catalog UI from the Global Header of the BI Consumers role.

In most cases, Dashboards have been designed and developed to encourage a desired navigation path and execution procedure.

For example: Filters are positioned on Dashboards to force users to run reports with chosen parameter combinations and guided navigation may be used to show and hide objects on the dashboards.

Dashboards may be hidden from the user as they are in development or have been decommissioned.

If users can run analyses directly from the Catalog UI they are able to bi-pass these processing rules put in place by the Dashboard.

Additionally, if the catalog has not been fully secured and users have been granted update permissions; they may also be able to perform tasks such as open, edit, delete, copy, rename, archive, unarchive, upload, view properties and view permissions of the catalog objects. This could lead to unwanted modifications being made on catalog objects as well as possible security violations of the source data.

 

Click on Administration (top right)

Click on Manage Privileges (under security)

 

 

Scroll to Home and Header -> Access Catalog UI -> Click on the BI Consumer role

 

 

Remove BI Consumer role and add BI Service Administrator (and other desired roles)

BI Consumers will no longer see the catalog

Click OK -> The new chosen roles will be reflected in Access Catalog UI.

Want to Learn More?

Click here for more A-Team OACS Blogs

Click here for more A-Team BICS Blogs

Click here for more A-Team OBIEE Blogs

Summary

This article identifies why an administrator may want to hide the Catalog UI from the Global Header of the BI Consumers role.

Additionally, it lists the steps necessary to modify who can view the Catalog UI from the Global Header.

The article proposes that it is undesirable for the BI Consumer role to have access to the Catalog UI and advises reserving this access to Administrator and Author roles.

Add Your Comment