As an example of a certain Tab we want to hide from a content editor would be a Developer Tab, which would be intended for developers only.

In our modularized component environment, for example, this would allow us to create a developer only tab where we could add unique classes to a component. This would allow us to scope our CSS to affect each use of the same component differently on the same page.

At the moment, our idea of how we could potentially restrict which user has the ability to view a dialog field/tab or not, would be based on a permission role.  And a property can just be added to the field or tab to tell Magnolia if this should be visible to the user or not.