# Using Object Pointer Field in CLP as Security for GraphQL Query Result

**URL:** <https://community.parseplatform.org/t/using-object-pointer-field-in-clp-as-security-for-graphql-query-result/908>\
**Category:** GraphQL API\
**Tags:** authentication\
**Created:** [October 5, 2020, 10:23pm UTC](https://community.parseplatform.org/t/using-object-pointer-field-in-clp-as-security-for-graphql-query-result/908 "2020-10-05T22:23:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![185driver](https://community.parseplatform.org/user_avatar/community.parseplatform.org/185driver/32/282_2.png) [@185driver](https://community.parseplatform.org/u/185driver)\
**Post date:** [October 6, 2020, 1:24am UTC](https://community.parseplatform.org/t/using-object-pointer-field-in-clp-as-security-for-graphql-query-result/908/2 "2020-10-06T01:24:44Z")

</div>

I found a couple of questions related to mine [here](https://community.parseplatform.org/t/permission-denied-for-action-find-on-class/365) and [here](https://community.parseplatform.org/t/clp-in-dashboard-problem/692).

If indeed I need to allow Authenticated `Read` access in my `Item` class CLPs for my query to work, I have to wonder what is the purpose then of setting a user pointer field CLP permission? It seems to have no discernible effect one way or the other.

---

_[View the full topic](https://community.parseplatform.org/t/using-object-pointer-field-in-clp-as-security-for-graphql-query-result/908)._