# Who’s new in June 2020

**URL:** <https://discuss.dgraph.io/t/who-s-new-in-june-2020/7084>\
**Category:** Users\
**Created:** [June 9, 2020, 3:33am UTC](https://discuss.dgraph.io/t/who-s-new-in-june-2020/7084 "2020-06-09T03:33:21Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![amaster507](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amaster507/32/4123_2.png) [@amaster507](https://discuss.dgraph.io/u/amaster507)\
**Post date:** [June 14, 2020, 12:58am UTC](https://discuss.dgraph.io/t/who-s-new-in-june-2020/7084/25 "2020-06-14T00:58:50Z")

</div>

Hi, I am Anthony from Oklahoma, USA. I am the developer of a new startup focused on assisting religous organizations. We launched a version of our SAAS Feb 2018, but are in the process of rebranding, refocusing, and rebuilding from the ground up.

We have been using GraphQL for a few months now backed by RDS and are getting tired of working around the limitation of a relational database driving a graph presentation of that data. Trying to decide which graph storage engine best fits our needs between dgraph and neo4j (4.0).

I am at a cross roads with ACL though as we want more granular control over properties and relationships like exists in neo4j but we see great things in the dgraph realm offering a quicker API build.

I have thought about putting a public GraphQL layer in front of a private GraphQL layer served by Dgraph. Has anyone done this for more refined ACL at a user level?

Here are some use cases we want to accomplish:

- restrict access to object properties depending on user role.
- restrict access to relationships between objects while allowing a user to still see both objects individually.
- restrict objects based upon user role (Dgraph can do this)
- specifically grant read access to only certain object properties based upon user role
- grant write access to only specific object properties based upon user role. (Neo4j still is lacking this too)
- grant read/write access to an object while restricting delete.

Also, there is also a typo on [Hello World | Basic | Dgraph Tour](https://dgraph.io/tour/basic/1/)

> A UID is not an edge, but can it be returned in a query with `uid` .

It should be “but it can be”

---

_[View the full topic](https://discuss.dgraph.io/t/who-s-new-in-june-2020/7084)._