Creating new column types in modern SharePoint lists and libraries

I think at a minimum, the option to control access to this function per location is necessary. We also use views, and not all views show all columns. What we've seen happening is that users want a certain field that already exists, but they think, "hmm, I want that 'date' column to show up," so they add a new Date column rather than switch the view or add the existing column (as Pieter suggests--great idea!).

I totally agree with Stephen--we need to empower users. But that doesn't mean all users are experts at IG in all situations. Sometimes data structures are created by teams through great discovery exercises, and all will benefit if the plan is followed by the whole team. One eager, well-meaning, but unfamiliar user can quickly ruin that. Control can empower users, too.

This new functionality is great is some scenarios. But we need at least the option to control when control is necessary.