See previous thread: https://answers.laserfiche.com/questions/51285/AddRemove-Fields-and-Sharing-Saved-Searches

Usually this discussion is headed off by talking about proper field security. Normally, I would agree that proper security is the best way to handle this issue. On the other hand, the "add/remove fields" button feels more like a "feature right" to me, something that ought to be turned on and off from the Administration Console, rather than broken down by individual field.

I would venture to say that in most implementations, users have no business adding fields that aren't already part of a template they are working with. There are rare circumstances, and usually this is a more advanced function.

I have an implementation I am working on right now, in which we are redoing metadata and folder structures across the whole repository. Users have added random, meaningless fields to documents across the repository that are not appropriate or necessary, but the users do have access to those fields because they need them on other templates they work with. We do not have the ability to say "You can modify this field on X template, but not on Y template." We could take away "Create" on that field, but then we would have to manage over 300 fields individually, when we would just rather no one (except the Workflow user) be able to add ad-hoc fields.

Would anyone else like to weigh in? I'd be interested to hear a counter point for why this shouldn't be an option to turn off. Again, I'm not advocating that no one should be able to add/remove fields - just that we should be able to assign this right to certain users and not all users.