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.
Does Oracle have any plans to introduce LLM-based AI features in a future release of Oracle Analytics Server (OAS) on-Premises? In particular, is there a roadmap for bringing capabilities such as the Oracle Analytics AI Assistant or an LLM-powered conversational chatbot, currently available in Oracle Analytics Cloud, to…
Summary of the Enhancement We request two key enhancements to the native Waterfall visualization in OAC Workbooks to support standard financial bridge reporting: Attribute-Driven Category Axis: Allow standard categorical attributes (with custom sorting) directly on the X-axis, removing the current dependency on Date/Time…
Currently in OAC, although we can create application roles in the OCI application (e.g Service Administrator), there is no way to programmatically create and configure custom application roles in OAC itself. This has to be done via the console system settings manually in OAC. We are running a large scale OAS > OAC…
Currently, in Oracle Analytics Cloud (OAC), there is a 250GB storage limit for datasets, but there are no practical management features to operate within this limit. This makes day‑to‑day operations very inconvenient.I would like to request the following enhancements for dataset storage management: Configurable storage…
I'm not very technical so if this is a non-starter or there's a solid workaround that already exists, please advise. We have users that query SQL data sources directly in other tools, but then would like to bring that query as a dataset to OAS. Ideally they could create the view in the database and reference that object…
