One could argue the privileges _are_ using a model. The model is the privileges model that controls all these things. I had originally thought it would be nice to get all this logic down in the local crud driving models as well, but what I'm seeing is that most of the time the privileges for the actions don't fit in a neat box like that. The actions are frequently transactions and other special behaviors. I don't think it will hurt anything to add function support for privileges, but in practice I expect that will just end up causing a large amount of indirection, and potentially code bloat, to be baked in.