Original User: mboeringa2010
One other remark concerning your issue:
It is best practice to use assign geodatabase Feature Class privileges to database "Roles" instead of to individual database "Users". I strongly advice you to do so, as it greatly simplifies privilege maintenance. If you assign your database users to individual groups that need specific privilege rights on certain Feature Classes, and than create a Role for that group of users and add all database users to that group using your database management system (e.g. SQL Server), you subsequently only need to assign all the needed geodatabase privileges to the single Role instead of potentially dozens or hundreds of users.
And if you wanted to know which users have what rights on a Feature Class, you simply first look at what "Roles" have what rights, and than use the database management console to look up which "Users" belong to that specific "Role".
Generally, you would also distinguish Roles not only based on which Feature Classes these users need to see / be able to use, but also based on whether or not they need to edit data.
So you might have a Role "Ramallah Editor" and "Ramallah Viewer", or a more specific Role "Ramallah Utilities Editor" and "Ramallah Utilities Viewer".