Related to TDV-I-449, but other implementation
TDV has the assumption that if someone is the owner of a view that forms the basis to another view, then they should also have access to that child-view.
In practice however it's very common for one team to make a set of views available to the other development teams, without them needing access to whatever that other team is doing with it.
The current setup causes a lot of source-owner-lack-of-privilige-to-child-view non-errors that through all the child views, obscuring actual errors, and causing endless call to the admins about when suddenly the entire board is filled with red flags just because the owner of the source view changed the privileges of the underlying view (like adding another group that has access).
I already suggested giving the error another colour (Which is relevant for admins), but really for the developers, it would be handy if you could just flip a toggle in the settings, and thus be able to ignore these non-errors all together.