Categories
Ability to control who is able to Export and what
Description
A feature to control who (user or group of users) is able to export from a project, as well as what are they able to export (e.g. anything from the project, only specific canvases from the project, visualizations that cannot be exported).
Use Case and Business Need
A project can be shared with an entire Org, however, only some people are allowed to download the entire or specific contents of that project.
Original Idea Number: 1d4b2a8a32
Comments
-
Would this be okay to enforce only for consumers? That is -- a project author could use them or change them and that is ok?
0 -
No , it should be done at user level for both Consumer and Project author.
0 -
This is critical feature to our role out.
0 -
Ability to control who can export the data from DV is a critical feature for us before we can to move to OAC. There is lots of sensitive sales & finance data in DV which we cannot let users export into a CSV and use them off line..we should have the capability to control who can export the data.
When can this feature be made available in OAC DV ?
0 -
I would definitely say this is a critical feature for Oracle and it's customers. With the number of data privacy and compliance processes that Oracle and it\'s customers are facing globally that will only increase, having the ability to disable the export at user, group and canvas is essential and not a nice to have. Whilst customers do need the ability to export for certain key approved users for the mass of any employee base Oracle and it's customer would not want an employee to be able to have data on their laptop or potentially then copy exported data for loading into an unapproved system or shared with a 3rd party either internal or external.
Oracle and customers have highly sensitive and competitive data within these solutions where they need to provide access to enable employees but need to ensure this is online only.
0 -
This is a base level access that needs to be managed and appropriately controlled. With how important this is to OSOC this should just be done. We cannot deploy this internally without it.
0 -
From an Oracle Corporate Systems Enterprise Architecture perspective, controlling the Export feature is a must-have for us to comply with and enforce several Security Compliance Requirements from GDPR, CCPA California Consumer Privacy Act and also Internal Oracle's Corporate Security and Compliance policies.
0 -
requested by NRMA for security reasons
0 -
This is critical to be in compliance with the Company Security policies
0 -
Since HCM data is crucial for HRBP's to refer with respect to their region and responsibilities, its important that we restrict the access to canvas and data visuals if possible.
Thanks,
Vinaykumar Byahatti0
