Here is just one example to illustrate why everyone needs a simple CRUD interface: Say you have an application that contains a large amount of information about your company’s clients, and this information is entered by uploading a large spreadsheet. What if someone notices that a name has been misspelled or an address has a typo?
Without a simple CRUD interface, there are two ways to change this data.
First, you could use another spreadsheet, but it must be prepared and uploaded. The original could be millions of rows long, and locating and correcting a single piece of data could be time consuming.
Another method to change that value is to contact the database admin and ask them to manipulate the data. This is highly discouraged, because the admin may not know how changing that piece of data could affect the performance of the application. The formatting of the data could be important, or the old piece of data could be relied on in other places.
But what if the application had a simple CRUD interface? You or another employee responsible for the data could change the data as soon as you find it - directly on the screen, without dealing with spreadsheets or going through the system administrator. The application would provide you the ease of directly manipulating the single piece of data, with the confidence that software performance will not be adversely affected by the changes. It would be as easy as seeing the problem, going to the screen to change it, and making the change!
It's also important to note that the CRUD interface can be restricted to the group of users who are responsible for maintaining the data. This way, they can manage the data easier while maintaining the application's security.
As you can see, a simple interface for modifying the data can save you a lot of headaches. By implementing CRUD interfaces for manipulating a single data entry, simple changes can be made quickly and safely.