'Hiding' Relationship Classes in Enterprise GDB

[JoeBorgione]

Version 10.3.1, SQl Server 2012:

Is there a way to 'hide' a relationship class in an enterprise geodatabse?  The users do not have any privileges to read (select) the feature class and table in the relationship class, but the relationship class itself shows up for them:

#relationship class #sde privileges‌ #privileges‌

[FrankSimeknaperville]

Eight years into this thread and this workaround confuses me.

The option (ArcGIS Pro > Options > Catalog Browsing > Browse project items > List only objects owned by the connecting user) is another added layer unto an already vast mosaic of options, configurations, settings, and preferences in the ArcGIS experience. Could an expert at Esri explain, technically, why the visibility of the relationship class object does not conform to the the same permissions set for both schema owners and database roles as they do for the feature classes and tables that participate in those same relationship objects? In other words - why is this an option, and, when would we ever NOT enable it?