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.…

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…