Sam, you say "not yet" does this imply this is in the pipeline ?
If so, an estimate as to when or which version it might be aimed for ?
I too would also like to use user attributes to be able to set a field's hidden attribute, this would be a very powerful and useful feature; it certainly gets my vote.
An extension of this would being able to set other attribute values such as: can_filter: , drill_fields: , sql: or concatenate an attribute values such as description: , label: or group_label: would be awesome; a great and easy way to highly customise a user's experience.
If my understanding is correct, the only current way to achieve column filtering at a user/group level, would be to maintain multiple copies of a model, and permission each model accordingly. This seems highly inefficient in general, but especially for our code base. Our model has many explores and each one many joins, often to the same view but sometimes joining in differnt ways. Any new joins or changes for a given explore would then need to be duplicated in each model. The models could then easily get out of sync with changes to one and not others !