If you have a look at the literature for the design of enums, in various languages, you’ll find clear patterns.
Nowhere in the Java documentation, or the Kotlin documentation, will you find examples of them being used for business logic like default values.
You can do it, but its not considered a good idea.
If using for any sort of configuration, when writing larger systems in Kotlin, I recommend adopting “DomainPreferences” classes, eg “EmailPreferences” to wrap groups of values, since they keep things like defaults and such in a single place, and they make it easy to test dependant services, since you can just feed them a POJO - what do we call POJOs in Kotlin anyway…?