Enhancement Request- Please provide restriction capability on the new OAC feature, Shared Objects inside a subject area. This is required such that we can have control in Production to limit the over utilization of this feature.
Organizations with larger user database will face significant challenges if there’s no capability to restrict access to shared objects. Relying on users not to save the shared objects they create isn’t an effective or sustainable control. This feature needs a proper access-control mechanism, and Oracle has acknowledged this, aligning with our view. As a result, we consider this a high-priority enhancement.
The feature is available.
Subject Area > Inspect dialog will show a new Access tab that will allow you to set user/group permission as Full Control vs Write. You will see a Consume option in the UI which is bug and will be removed with September 2026 update.
We’ve identified the Consume option appears to be a defect: when we change a role’s subject area access from Write to Consume, it automatically reverts back to Write.
Our requirement is to retain full control over the “Share Objects” capability tied to subject areas in OAC solely to Admin users, particularly in Production. Given the size of our user base, we can’t allow users to freely create or modify objects based on individual needs, as this will quickly lead to an unmanageable set of artefacts.
Relying on user guidance to self-restrict object creation/editing isn’t a viable control for Production.
Only Administrators can update the Access permission on Subject Area > Inspect. Access tab will not be shown for non-admin users in the SA> Inspect dialog.
On Datasets, the dataset owner controls the Access.
Following the September 2026 software update, we observed that the Inspect dialog now provides only the Full Control and Write options. However, there’s still no capability to restrict access to shared objects created within a subject area.
As a result, a shared calculation created by one user can be edited and saved by another user. This isn’t appropriate for a production environment, as it could lead to users modifying one another’s calculations and creating unnecessary clutter.
We need more granular access controls to ensure that shared objects can be managed only by authorized users (Admin) and to maintain a controlled, well-governed production environment.
How to schedule 'Generate Audit Report' monthly 2nd day , so that it generates output for the last month We have tried creating new custom job similar to Generate Audit Report and enabled Date Argument Numbers (1,2) which is the date parameters , but it was not returning the data as expected. Its taking the number of days…
There are more menu options made readily available by default to non-admin users that we wish to restrict. It seems this functionality, to control menu options in the user button menu on the upper-right-hand-side of OAC (DV), is not currently available. Can we be given the ability to customize this menu? Ideally via…
Right now once you save a workbook, that's it. If you (or someone else with edit access) changes a canvas, deletes a calc or messes up a filter and saves, there's no easy way to get back to how it was. The options are digging out an old .dva export if you happened to take one, or asking an admin about a snapshot, which…
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…
