Categories
Data Level Security for Data Set
Description
Allow users to define Data level security on a data set directly.
Use Case and Business Need
It will allow business analysts to directly define the data level security without having to request the change in the RPD.
Original Idea Number: ffb46e5e02
Comments
-
Excellent idea.
0 -
There should be the capability to define rules for Row Level Security by named user or Role.The access to the data set would still be governed through standard DV permissions. The rules should be transferable to additional data sets containing the same dimension members.
0 -
Hi Sandhya,
This Idea for Row Level Security has also been created.
Please Vote in support of the idea from this link: https://cloudcustomerconnect.oracle.com/posts/75e7ed0ce8
Best,
Brendan
0 -
Such like in excel dashboard, we may compile summary for readers, at same time we could hide the raw data tab and lock the file. So readers are all fine to view summary but can't view raw data. Raw data contains with lots of information, so this is same for data set. It is better to turn off the data set downloading by others or permit the dashboard owners set security level to OAC dashboard and its data set
0 -
These are good comments. We are starting the design work in this area and will keep this in mind.
0 -
I'm an Oracle employee in an internal role supporting the reporting of progress against process improvement initiatives across the globe. I've created data flows which ingest security provisioned data from SI-DV Leads and Opportunities by PG data and then append (UNION) Target data from an XLS file to create a master data set. When I publish the final data set and display results in a dashboard, the users currently have access to global results and not what they are individually provisioned access to (i.e. North America).
Would love to have the ability to add users or roles where I can specify the data they have access to either in the dashboard or data set (i.e. a filter for users based geo's and products).
0 -
As an internal implementer of OAS, I can say this is an often-requested feature from our customers. We've implemented manual workarounds for it at the database level but having it on the Datasets themselves is the ideal solution.
0 -
Implementing row level security (using a security table joined into the dataset), is a planned feature for multi-table datasets.
0 -
Will this capability be somewhere attached to OAC Classic as well ?
0 -
