For companies which have multiple products which each have multiple environments, what is the best practice for managing the number of projects in the Descope console? We currently have two separate products which each have 10 environments (and thus 10 separate projects in the console). We are using the terraform provider to manage our configuration. Does Descope have any guidance on this? Also, is it on the roadmap to have the project id be a part of the URL in the descope console so we can link to to specific projects?

For managing a large number of projects, we have several major customers overseeing numerous active projects for development/etc. Some of which spin up and tear down 20 or more projects per day for E2E testing and what not. What are you currently struggling with in terms of managing these? General clutter, keeping track of envs, etc?

Hi @Chris Carper Thanks for the reply. We're concerned about keeping track of envs and clutter. At present we are managing 20 projects in descope as well as the temporary projects we spin up for testing. I'm really just asking if the all projects in account strategy is what most companies do, or if there are ways of managing such situations that we're not aware of. We want to make sure that we're not boxing ourselves in with the approach of putting everything in one terraform config and one account. Only to later learn that there's a better way.

Generally within one account (Company as we describe it) is the most ideal; however, should you have it all in one terraform config? Or have it split out into the terraform config for different products and envs? I feel like splitting the terraform config out makes more sense since then you can iteratively release rather than a full release across all projects

Thank you, Chris!