Currently the protection group MIR.PUBLIC is associated with general user and the public collections are associated with MIR.PUBLIC, but some unknown issue is causing the problem. NBIA development team could not replicate the problem. The workaround is to add the NBIA.PUBLIC protection group which is hard-coded into NBIA to be "Public".