Reading through a few different threads, I was able to find that the Principal Object Access (POA) table in Dynamics will give me information about what records have been shared with Users. Using PowerBI, I have developed a Report that looks at this table, along with our Account and SystemUser tables for decoding, and we can now see what records are shared, with whom they are shared, and what level of share has been given. The issue I am running into now is that if you share a record with a User, a record is created in the POA, and even if you remove the shared access, the record still remains (the AccessRightsMask permission field is just set to "0" for no access). To give an idea why I am using this table in the first place, we have a field in Dynamics where we list a "secondary" salesperson for Account records. We are going to assign Ownership of the record to the "primary" salesperson, and share the record with the secondary salesperson (I know we can accomplish this through other means, but this strategy is going to work best for us). I planned on using the PowerBI report to show all records that have a secondary salesperson, but do NOT have any shared access to the record. The report works, EXCEPT if we ever shared the record with someone then removed that shared access, as the "ghost" record will still exist. I would no longer be able to filter my report to show me only records where the Shared User is blank, as I would be skipping the "ghost" records. Does anyone know if the POA table will clear these records periodically? If not, is there any way I can purge these records (where both the AccessRightsMask and InheritedAccessRightsMask fields are set to 0)? I am new to the POA table as a whole, just figured out how to connect to it using PowerBI a few days ago. I know this will be the key to solving our "shared access check", and any additional info is greatly appreciated. Thank you! :-)