Restrict Permissions to Create Custom Views

[MrBean]

Currently, I don't like how there is no way to restrict users from adding a new custom view to an index page. . .  

This results in the following problems at the enterprise level: 

1) Lot's of duplicate views 

2) Inconsistent columns / properties included

3) Innacurate filtering

4) Having to log in every account to remove a view just to delete/archive an old property.

In a perfect world, it would be awesome if we could set permissions up so that the team lead is the only person able to add custom views. 

Thus non-managers need to run their requests through them or the admin. Standardizing would greatly improve their experience with views. 

[FOrsini]

It would be a "killer application".

We also really need to avoid hundreds inaccurate views. The administrator shall choose witch view a user can have in his dashboard so that he can view the correct fields (and them only).

[LLongoITC]

It would be a great improvement to manage easily the views by limiting the creation permission.

For our business, it is crucial to have well-defined views on a specific set of fields using a number of different views made by management team. The capability to assemble custom views, in our use case, let the user focus on a mix of fields that, in some cases, point the interest on less important facts that however make impacts on results.
Please take in account this request.
Thank you.