Help with fixing inherited domain permission

[Tony Broadbent]

Hi all,

I've inherited an old Google drive setup, with many folders created in 2014, thousands of files and hundreds of users.
Folder B is in Folder A. 
Folder B is owned by user B. 
User B does not seem to be able to see Folder A (GAM reports: "Show Failed: Does not exist

").
Folder A fileinfo lists domain has (inherited) reader permissions, so surely user B and all other domain users should be able to see Folder A.

ChatGPT seems to have an unreliable understanding of GAM, but suggests this is a problem with legacy folders and inherited permissions.
Before I break something important, can anyone suggest how to fix this folder, and/or how to find any other such problems within my environment.
Many thanks,  
Tony.

[Gray Biggs]

Hi Tony, I believe Google changed how permissions work in Drive fairly recently. 

For a while, I was creating my own structure where Folder A was given view access to a certain group. Folders B through Z were inside Folder A, and I pulled all permissions for that group except for the exact folders I wanted particular members to see. So anyone could open Folder A, but were only able to see the particular subfolders I gave them access to.

This no longer works; if I gave gr...@domain.com view access to Folder A, I could not take away view access from gr...@domain.com on Folder B without ALSO stripping it from Folder A. The folders I had created before still function in the way I designed them, though.

That is to say, I could definitely see a 10 year old Drive having old permissions that no longer make sense.

Are you able to explicitly grant User B access to Folder A and see if that changes anything?