nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Option to prevent Users with Author role access to "Create Connection"

Bangar Aaloori

All Users with FDI "Author" role should not have access for using "Create Connection". This would unnecessarily give unauthorized access and by using that connection will expose FDI to external systems/applications. There should be an option to change the configuration settings or customize "Author" role so that "Create Connection" is disabled for defined Users.

Find more posts tagged with

Delivered

Status: Delivered

Comments

Daniel Chapman

We certainly have a use case where we need to restrict the ability of the "Author" role in FDI and agree there should be an ability to disconnect this privilege to prevent ability to expose FDI to external data. A custom role should be possible to allow customers to manage the privileges of the "Author" role.

Cheryl Gover

This is a good idea to be able to restrict "Author" role to not have the ability to create connection. Not all users will need to create connections and adds risk to giving the role.

T.Robinson

Further segmentation of roles/privileges is an overall them that should be addressed by Oracle. This idea would be helpful.

Jacob at MKL

I agree! Would be a nice addition to be able to change the configuration settings for this.

Gabby Rubin-Oracle

OAC/OAS customers can define a user role that allows the creation of only specific types of assets (e.g., create workbooks but no connections). This is done using fine-grained permissions.

https://www.youtube.com/watch?v=nstop2I4pYo