# Namespaces creation and their lifecycle

**URL:** <https://community.temporal.io/t/namespaces-creation-and-their-lifecycle/5986>\
**Category:** Community Support\
**Tags:** namespace\
**Created:** [September 15, 2022, 8:14pm UTC](https://community.temporal.io/t/namespaces-creation-and-their-lifecycle/5986 "2022-09-15T20:14:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazzy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/mazzy/32/2772_2.png) [@mazzy](https://community.temporal.io/u/mazzy)\
**Post date:** [September 15, 2022, 8:14pm UTC](https://community.temporal.io/t/namespaces-creation-and-their-lifecycle/5986/1 "2022-09-15T20:14:27Z")

</div>

One thing that I haven’t found chatting around is a consolidated and recommend approach on how keep track of namespaces.

The creation of a namespace is regulated via the grpc api which is leveraged by the temporal client and temporal sdks.

What I would like to achieve is for instance an infrastructure as code approach where we keep track of namespaces and their properties under vcs and regulate access to the cluster.

Naturally due to the age of temporal project, solutions that wrap its api aren’t much but I would like to ask beforehand whether the temporal people recommend any way how to handle namespaces.

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [September 19, 2022, 11:45pm UTC](https://community.temporal.io/t/namespaces-creation-and-their-lifecycle/5986/3 "2022-09-19T23:45:02Z")

</div>

You could restrict access to certain client apis via [authorization](https://docs.temporal.io/server/security/#authorization) which you could customize.  
Dock for [authorizer](https://docs.temporal.io/clusters#authorizer-plugin) and [claims mapper](https://docs.temporal.io/clusters#claim-mapper).  
Temporal has default claims mapper based on JWT.  
Here is relevant [config](https://github.com/temporalio/temporal/blob/master/docker/config_template.yaml#L279). You can set both values to “default” to configure default authorizer and claims mapper. If you define your own I believe you would need to rebuild server image.

---

<div class="post-metadata">

**Author:** ![mazzy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/mazzy/32/2772_2.png) [@mazzy](https://community.temporal.io/u/mazzy)\
**Post date:** [September 20, 2022, 5:23am UTC](https://community.temporal.io/t/namespaces-creation-and-their-lifecycle/5986/4 "2022-09-20T05:23:58Z")

</div>

Thanks Tihomir for the recommendation. However you are referring to authz/authn for a namespace. I’m asking how to keep track and manage the lifecycle of. Namespace. Not sure the things are correlated.