reading and writing app configs to the database and defining if ther are editable or not?

Hi 

we have recently decided to transfer all our app configs to the database.

right now we consider all these configs to be both readable and writeable.

but we want to future proof it so that if a certain client decides to make a certain category of configs to be only readable we could manage it.

at the moment a single business object reads all the configs from the database and stores them. 

the following is a simple schema representing our table.

CREATE TABLE GlobalSettings
(
    SectionName VARCHAR(50),
    SettingName VARCHAR(50),
    SettingValue VARCHAR(1000),
    SettingType TINYINT
);

my question is that how should we design our class so that we can achieve this?