We found a solution on hiding the oracle delivered reports to the end users. For the group that you are delivering the reports to, the content duties that overlap with the oracle reports need to be removed from them.

For example, if you have a custom group that has one of the duty roles above assigned to them then they will be able to see the oracle reports. Let me know if this makes sense or helps you!

All comments

Sumanth V -Oracle

@AmitD -This is expected behavior. Out-of-the-box (OOTB) workbooks are locked, and no changes are allowed, including modifications to permissions. The same applies to the 'Oracle' folder, which stores these workbooks.

AmitD

Why Consumer role permissions also restricted for this folder

Sumanth V -Oracle

@AmitD - It's basically locked per design. No users can delete or even rename the OOTB workbooks.

Cade Johnston

I agree with @AmitD with this. It would be helpful to hide the Oracle folder due to creating custom groups that have the application roles that are also available to some of the reports in the Oracle folder.

Mallikarjuna Kuppauru-Oracle

Hi @AmitD , @Cade Johnston

Can you please log an Idea's lab Request for your business case, Based on voting team will review further.

Regards,

Arjun

Kevin Riedy

Hello, we are interested in being able to hide the delivered folders as well. Was there ever a resolution on this?

Cade Johnston

Howdy @Kevin Riedy!

For example, if you have a custom group that has one of the duty roles above assigned to them then they will be able to see the oracle reports. Let me know if this makes sense or helps you!

Kevin Riedy

Hi @Cade Johnston appreciate you following up. This makes sense. Thanks for the update!

Pallavi Srivastava-Oracle

Hi @Cade Johnston , I have a similar ask where Oracle delivered folders should only be seen by Service Admin. I tried removing all other content duty roles from a folder but it shows error while saving. Basically - does not allow to delete and save the new access. How does it work for you?

JT_DC_2023

Hi all,

For those struggling with user groups seeing the out-of-the-box (OOTB) Oracle content folders when they should not, here’s a quick explanation and solution:

This issue arises because users or groups assigned application roles with "Content Duty" at the end automatically gain access to Oracle’s OOTB content (folders and workbooks).

To prevent users from seeing these workbooks or folders:

Remove the "Content Duty" roles from their application roles.
Assign only the "Duty" roles for the respective subject areas where users should have access to data.

Key Difference Between Roles:

Duty Role: Grants access to the subject area and its data
Content Duty Role: Grants access to Oracle’s OOTB folders and workbooks

Hope this helps!