sure.
we need AEM to host content in a headless manner. exposing content via GraphQL is promising.
in some use cases we need these content to be protected:
- if someone get the URL of these content they cannot load them in browser unless login.
- protected content need to be separated by roles also. role A users can not see content belongs to role B users, after login.