Hi GrowthBook Team, I’m currently working with multiple projects within GrowthBook and ran into an issue I was hoping to get clarification or help with. I’d like to use the same feature key (e.g., ledger_configs) across different projects, each with its own configuration and environment settings. However, when I try to create a feature with a key that already exists in another project, I get the error: “This feature key already exists. Feature keys must be unique.” From my understanding, feature keys are enforced globally rather than scoped per project. This makes it difficult to manage configurations that are logically the same (by key) but need to differ per project context. Is there any current or planned support for allowing the same feature key across different projects? Or alternatively, is there a recommended way to handle this use case? Thanks in advance for your help! Best regards,

As you mentioned, you can create a global flag (not connected to a particular project) or a per-project flag. The key is essentially the flag's ID, which links it to the different config/env. I think your best bet will be duplicating the key for each project. There's no plan to change this behavior, but I'd love to know more about your use case.