(Submitted via Intercom)
There are multiple aspects: controlling creation of new custom fields vs editing of existing ones vs hiding existing ones. They all come down to finer-grained permissions over managing custom fields. See also: https://clickup.canny.io/feature-requests/p/restrict-who-can-create-custom-fields
See also: https://clickup.canny.io/feature-requests/p/ability-to-hide-custom-fields-from-some-users
See also: https://clickup.canny.io/feature-requests/p/custom-fields-for-selected-users
See also: https://clickup.canny.io/feature-requests/p/consolidate-custom-fields
IMO, there needs to be more separation between editing a view (what appears on the screen, how it appears) vs editing the underlying metadata (which fields exist, what they contain, deleting fields, etc.). This is bound to cause a problem if someone thinks they are "deleting a column from a view" when they are really "deleting a column".
I hope it will be possible to decide what fields are hidden or maybe even visible but not customizable for 'normal' users. e.g. budget estimation is an example to make not editable..