title: Is it possible to fine-tune access control in Hyperledger Fabric private data collections further than restricting entire organizations?
body: <p>In the <a href="https://hyperledger-fabric.readthedocs.io/en/release-1.4/private-data-arch.html#private-data-collection-definition" rel="nofollow noreferrer">Hyperledger Fabric Docs</a>, while reading about private data collections I came accross this sentence regarding memberReadOnly:</p>
  
  <blockquote>
    <p>Utilize a value of false if you would like to encode more granular access control within individual chaincode functions.</p>
  </blockquote>
  
  <p>If I understand this correctly, this allows me to code into the smart contract specifications that will allow me to limit control to eg. specific clients of one organization instead of all peers of member organizations.</p>
  
  <p>If that is so, I am curious as to how this can be done in the contract. Is there a specific way to handle access control or is it at my own discretion to write code that will enforce it? If you can provide me with any examples it would be very helpful.</p>
  
  <p>To clarify what I mean, I come from Ethereum and what I am essentially asking is whether there is something like the require method in solidity, or would I just use a simple if.</p>
  
  <p>Thanks for any help. If you close question for wrong site, please point me to the right place as I have not been able to find somewhere more relevant.</p>