QLDB seems to be this centralized extension built upon the Fabric orderer service that allows you to query a replication of the blockchain network in an SQL-like manner.
With the different orgs on the network, I was wondering how QLDB handles permissions? It wouldn't make sense for every member to have full access to all data in QLDB, so is there some built-in method of access control for specific parts of the data?