# The Need for Update auth after logic

**URL:** <https://discuss.dgraph.io/t/the-need-for-update-auth-after-logic/10298>\
**Category:** GraphQL\
**Tags:** kind:feature\
**Created:** [September 11, 2020, 2:32pm UTC](https://discuss.dgraph.io/t/the-need-for-update-auth-after-logic/10298 "2020-09-11T14:32:00Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![jdgamble555](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/jdgamble555/32/7503_2.png) [@jdgamble555](https://discuss.dgraph.io/u/jdgamble555)\
**Post date:** [June 20, 2021, 5:17am UTC](https://discuss.dgraph.io/t/the-need-for-update-auth-after-logic/10298/9 "2021-06-20T05:17:11Z")

</div>

> [@arijit](#):
>
> But we may need to decide if we want to add this in auth directly.

Can we please get this implemented! This desperately needs to be added to the @auth directly. Without this, it makes the add @auth pointless, as I can simply add something and change it later.

It should be a simple fix as you already have [before and after validation in the code](https://github.com/dgraph-io/dgraph/blob/master/graphql/schema/auth.go). I believe this should be moved to the **TOP of priorities**.

It also opens up a can of new features as I mentioned [here](http://discuss.hypermode.com/t/moving-graphql-authorization-to-admin-api/13304/3) when it comes do validation.

Please and thank you!

J

* * *

FWI

> [@amaster507](#):
>
> Looks like it’s on the roadmap

No, hooks are a different feature, and only one of the two was actually added.

---

_[View the full topic](https://discuss.dgraph.io/t/the-need-for-update-auth-after-logic/10298)._