"Allow Public Entries" Expansion
In most cases, the "allow public entries" is really limited to whether the user can create public Address Book entries or not. However, I think the concept is more granular than that.
I want users to be able to create public Address Book Entries, Notes, and Documents - but for the vast majority of users, I do not want them creating public Column Setups / Search Catalogs / Email Templates / etc. Often times, users will create these items without realizing what the implications are and it leads to clutter across the program. Certain users (department heads, admins, power users, etc.) should be allowed to create public objects which are shared across departments as required - but it would be nice to prevent users from inadvertently cluttering the database with public stuff while still giving them the ability to create the public objects that they should be creating.