Parameters about negotial rules in database is a good pattern?

I just would like to know if is considered a good design pattern or smell code to save information about negotial rules of my application in my database. For example, I have a situation where is possible to enable or disable some feature's system and I prefer to record this in some table, because that is easier to change this feature just using a SQL script in my database environment. To do that is considered a good design pattern?

Tks.