Access Control Issue: DV Datasets Visible in Classic Analytics

Question

We have observed that, by default, Data Visualization (DV) datasets appear in the “Create Analysis” list under Classic Analytics in OAC, regardless of specific user or role permissions.

The background of this issue is that the user currently holds the BI Author role. With this role, users are able to create Classic Analytics reports using Subject Areas within the OBIEE 12c / OAS environment.

At present, we have two functional reporting areas designed in BI:

* Finance
* HR

We have shared an HR Data Visualization (DV) report with the user under read-only access (DV Consumer role). However, since the user also holds the BI Author role, they are able to create Classic Analytics reports using datasets that they can access.

For example:

* Finance DV Reports Role: DV Consumer – User can only view DV reports.
* HR Adhoc Reports Role: BI Author – User can create Classic Analytics reports.

Kindly review and advise on the appropriate solution

Jayaram Bodagala · Answer

Hi @Mohammed Rafi

Thanks for the sharing details.

As noted above, the user has already been assigned the BI Author (HR Adhoc) role. We now need to share the Finance DV workbook with the same user. Since the user also holds the BI Author role, they can create Classic Analytics reports using any datasets to which they have access.

Please let me know how we can hide or restrict specific datasets from appearing in the Create Analytic menu.

Mohammed Rafi · Answer

If my response has answered your question, please mention the thread as Accepted Answer as this will help the community members on the solution

Mohammed Rafi · Answer

Your Current Role Design (Root Cause)

From your setup:

Area

Role

Result

Finance DV

DV Consumer

View only (correct)

HR Adhoc

BI Author

Can create Classic reports

DV Dataset (HR)

Accessible

Appears in Create Analysis

The key conflict:

BI Author + Dataset visibility = Dataset usable in Classic Analytics

Restrict Dataset Permissions (Most Direct Fix)

Instead of only sharing the DV report:

* Go to: DV Dataset → Permissions
* Remove access for the BI Author users/groups
* Only grant access to intended DV Consumers

This ensures:

* Dataset will NOT appear in Create Analysis
* Even if user has BI Author role

👉 This is the cleanest and Oracle-recommended approach.