# Name/label for multi tenancy namespaces

**URL:** <https://discuss.dgraph.io/t/name-label-for-multi-tenancy-namespaces/14786>\
**Category:** Dgraph\
**Tags:** enterprise\
**Created:** [July 1, 2021, 11:13am UTC](https://discuss.dgraph.io/t/name-label-for-multi-tenancy-namespaces/14786 "2021-07-01T11:13:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulrostorp](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/paulrostorp/32/1091_2.png) [@paulrostorp](https://discuss.dgraph.io/u/paulrostorp)\
**Post date:** [July 1, 2021, 11:13am UTC](https://discuss.dgraph.io/t/name-label-for-multi-tenancy-namespaces/14786/1 "2021-07-01T11:13:34Z")

</div>

Currently, all that identifies a namespace is the auto-generated ID you get when creating it.

In a scenario where a cluster has a high number of namespaces, if that namespace id is lost, it might be quite difficult to find out which namespace is which…

A solution to this problem is having the ability to give a namespace a uniquely identifiable name to a namespace. This may be a replacement to the integer namespaceId or an additional property.

---

<div class="post-metadata">

**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\
**Post date:** [July 1, 2021, 1:05pm UTC](https://discuss.dgraph.io/t/name-label-for-multi-tenancy-namespaces/14786/2 "2021-07-01T13:05:03Z")

</div>

That was discussed internally, but the conclusion was that this isn’t necessary and would bring complexity to the code. Also, we gonna have a way to manage namespaces in the Cloud UI. It should be available soon.