Limit a group of users or an application role to only certain DV permissions. For example, a group can only have the permission to upload data files, and cannot create other DV objects, such as data flow, workbooks, etc.
This is a great feature that allows for more granular control over permissions and ensures that certain users only have access to the specific actions they need. It enhances security and helps to prevent accidental changes or unauthorized access to sensitive data.
There is work being done around fine-grained permissions.
@Adam Bloom-Oracle FYI
Hi Bret,
Which version are you talking about? Can you please guide us to set it up in the latest version of OAS 6.4? We need an application role to load spreadsheets into DV, but it cannot be granted additional DV Analyst permissions.
Thanks,
Linda
This is good idea and there is definitely business use cases over granular access to parts of dvanalyst role such as just being able to load data files by business users.
The current ETA is the November update for OAC (and OAS 2024). It might still change if we will encounter any last-minute issues.
Right now, OAC offers pre-built pages and watchlists related to NSAW. At our University, we do not need these pages, and we want to delete them entirely. We've been told in response to our SR that all we can do is keep "Access" limited to only the default admin and sysAdmin roles. This prevents regular users from seeing…
It would be nice to have a way to right click on an object (subject Area, Column, Calculation, etc.) in the Data Panel and show where that object is referenced in a workbook = canvas, visualization, filter, calculation, data action, etc.) In Workbooks with multiple canvases and multiple subject areas, we are left to hover…
We want to automate the workbook export to .dva file and import this into another OAC instance using REST API, The goal is an OCI DevOps pipeline that can promote (a) a whole folder, (b) a single workbook, or (c) several workbooks in one run to another OAC instance, and print a status result at the end. Blocker: Export and…
When Oracle Analytics AI features find an anomaly, trend or key driver, let authors save those results as a dataset or subject area. Each run would add rows with the metric, the date found, the expected versus actual value, the severity, the main drivers and the filters applied. Authors could then build workbooks, schedule…
We use the snapshot to update AppRoles members. But we would like to disable catalog content to have smaller snapshots and create snapshots faster.
