Sync Content and Configuration Between Sandbox and Prod Environments
backlog
U
Usama Ansari
Today, Sandbox operates independently from Prod, which creates practical issues. When testing KB Widget behavior, Prod has 600 plus URL mappings, and maintaining the same setup in Sandbox is not feasible, especially when Sandbox is meant for QA and Dev testing.
While Dev and QA environments closely mirror Prod, the Document360 Sandbox does not. This limits its usefulness and turns it into additional overhead that requires frequent manual updates across Prod and Sandbox.
Previously, we could deploy documentation to Dev and QA. This is no longer possible. The KB Widget router supports only one auth URL, and Sandbox contains outdated configurations. Keeping it current requires significant manual effort that should be automated.
This feature request requires auto-sync of both content and all configuration and settings between Prod and Sandbox. This removes redundant manual work, keeps environments aligned, and allows Sandbox to be used for validation and testing without friction.
Log In
D
D360 Product Management
marked this post as
backlog
Mohamed Shakheen
Hi Usama
Thanks for outlining this in detail - this clearly highlights the operational friction caused by the current Sandbox–Prod separation.
At this point, automatic syncing of content, configuration, and settings between Prod and Sandbox is not part of our current product roadmap. The Sandbox environment is intentionally designed to operate independently, and enabling full parity with Prod would require foundational changes to environment isolation, deployment, and security models, which are not planned in the current cycle.
We acknowledge the limitations this creates for realistic QA and widget validation, especially for complex setups with extensive URL mappings and authentication dependencies. We’ve captured this feedback and will continue to evaluate it based on customer demand and overall impact. If this emerges as a broader requirement across multiple customers, we’ll reassess its priority in a future roadmap iteration.