# Putting it All Together - Dgraph Authentication, Authorization, and Granular Access Control (PART 2) - Dgraph Blog

**URL:** <https://discuss.dgraph.io/t/putting-it-all-together-dgraph-authentication-authorization-and-granular-access-control-part-2-dgraph-blog/10719>\
**Category:** Blog\
**Created:** [October 1, 2020, 12:18pm UTC](https://discuss.dgraph.io/t/putting-it-all-together-dgraph-authentication-authorization-and-granular-access-control-part-2-dgraph-blog/10719 "2020-10-01T12:18:00Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![ansonhwang](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/ansonhwang/32/9117_2.png) [@ansonhwang](https://discuss.dgraph.io/u/ansonhwang)\
**Post date:** [January 15, 2022, 8:03am UTC](https://discuss.dgraph.io/t/putting-it-all-together-dgraph-authentication-authorization-and-granular-access-control-part-2-dgraph-blog/10719/13 "2022-01-15T08:03:16Z")

</div>

Should I throw a graphql error in resover? how to throw it in node js?  
where is the action of verified should take placed? the resover too?

There is so little information about this, any detail will be appreciated.

---

_[View the full topic](https://discuss.dgraph.io/t/putting-it-all-together-dgraph-authentication-authorization-and-granular-access-control-part-2-dgraph-blog/10719)._