The database designer and administrator probably always be asked the following questions:

• What's the best way to avoid any unintended DML activities in a table?
• How to keep database data with consistence?

As described in attached article, the author mentioned couple ways to perform this goal.

• control application through an application interface, such as forms
• disable table lock to avoid DML activities
• limit privileges by maintaining user profiles table product_profile
• use flashback to revert data if it's changed unintendedly
• use trigger to prevent data from unintended changes
• use views to present data and reduce the impacts of DML
  

Among above ways, I would like to say maintaining user profiles table product_profile is quite straightforward way. Because, a well-designed application system should reduce this kind of risk to minimum and user should be keep away from unintended DML changes. Comparing to users, developers have more privileges, especially they can log on SQL*PLUS to directly manipulate data. Therefore, maintaining user profiles table product_profile is a good approach to limit their DML activities. For more information about this, please visit https://netfiles.uiuc.edu/jstrode/www/oraplus/product_profile.html

Please find attachment for complete article "Protecting Data from Users".