MVC3 / EF Code-First: Modelling a scenario where an admin can control read-only / view / defaults for certain user-input fields on web pages?
===

I would like the admins to control default values, and determine whether an input field is defaulted / can be written/seen by users.

A couple of ideas I had were to: 
- Include one 'default' record that the admins can update, and then grab the values every time a user creates a new entry. In this scenario I'm not sure how to control readonly/view. 
- Create a structure that uses 'field' objects, and in the 'field', include bools for read-only/viewable, and a field for the actual field type and default. The downside is that the table that holds the users' entries would be a subset of this set of objects. Also I am not sure how complex this structure is going to end up being, with regard to client/server validations, etc.

If it matters, we are using ASP.net MVC3, with Code-First Entity Framework 4.1. Another idea was to change the annotations at runtime, which seems complicated and maybe hard to maintain/easy to screw up.