# Missing New Config Sandbox option

**URL:** <https://community.shotgridsoftware.com/t/missing-new-config-sandbox-option/14519>\
**Category:** Pipeline Integrations\
**Created:** [January 20, 2022, 8:22pm UTC](https://community.shotgridsoftware.com/t/missing-new-config-sandbox-option/14519 "2022-01-20T20:22:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mathurf](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/mathurf/32/255_2.png) [@mathurf](https://community.shotgridsoftware.com/u/mathurf)\
**Post date:** [January 21, 2022, 1:38pm UTC](https://community.shotgridsoftware.com/t/missing-new-config-sandbox-option/14519/2 "2022-01-21T13:38:54Z")

</div>

Hi Trevor,

`New config sandbox` is available for distributed configs, maybe your project is using a centralized config?.

Here is a post about distributed config management:

> [@Distributed config management workflow](https://community.shotgridsoftware.com/t/distributed-config-management-workflow/232):
>
> I’ve seen the question come up a few times around how to test configuration changes and push them to production when using a [distributed config](https://developer.shotgunsoftware.com/tk-core/initializing.html#distributed-configurations) setup. My personal recommendation would be to do the following: Assuming your project already has a “primary” PipelineConfiguration entity with an uploaded config, I would create a second one called dev. Set a [dev descriptor](https://developer.shotgunsoftware.com/tk-core/descriptor.html#pointing-to-a-path-on-disk) to define a location to your config on disk. (If you haven’t got a config on disk you can download the primary config and unzi…

Hope that helps.  
Francis

---

_[View the full topic](https://community.shotgridsoftware.com/t/missing-new-config-sandbox-option/14519)._