This message was deleted.

Hi there! You're right that we don't currently support nested namespaces. In your use case, I'm understanding that you want to run mutually exclusive experiments on the same data without overlap/interference. Is that right?

Hey Ryan! 👋 That’s exactly right, our teams need a way to move autonomously and we want to enable them, while also having a scalable approach to manage their experiments. I found that coupling a Saved Group (Attribute) directly with a namespace - creating each and attaching both to the override rule to each ff can segment traffic in a single piece of the flow, that the Saved Group covers. And then we need alignment in our organization based on these limitations. I found this issue that might be covering some of this functionality - but I don’t know how much work it is exactly to contribute! https://github.com/growthbook/growthbook/issues/490 Let me know if you have any other suggestions on what we can currently do. Thanks so much!!

I chatted with our engineers and data science teams. At the moment, there's not a clear way to achieve this; however, they recognize the validity of the use case and are investigating the possibility of nested namespaces. If I get any additional info, I'll share it with you.