# Constraining the number of config nodes

**URL:** <https://discourse.nodered.org/t/constraining-the-number-of-config-nodes/11398>\
**Category:** Developing Nodes\
**Created:** [22 May 2019 03:08 UTC](https://discourse.nodered.org/t/constraining-the-number-of-config-nodes/11398 "2019-05-22T03:08:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![uma](https://avatars.discourse-cdn.com/v4/letter/u/ba9def/32.png) [@uma](https://discourse.nodered.org/u/uma)\
**Post date:** [22 May 2019 03:08 UTC](https://discourse.nodered.org/t/constraining-the-number-of-config-nodes/11398/1 "2019-05-22T03:08:44Z")

</div>

Hi  
I am creating config server nodes for my custom node- I am following [https://nodered.org/docs/creating-nodes/config-nodes](https://nodered.org/docs/creating-nodes/config-nodes). Is there a way to constrain the number of config nodes created? As an example, I would like to not show/enable "Add new config..." when there is already a config present. Or if that is not possible, I need to be able to validate the new config so that duplicate entries are not configured.  
Thanks  
Uma