Mindset gives you somewhere to build that is not live: named partitions inside your Mindset organisation, normally Test and Production, each with its own connections. If somebody asks whether there is a sandbox, this is the answer.
What an environment holds
Not a copy of your work, and not a permission level. An environment is a wall. Everything built inside one belongs to it and cannot see anything in another.
What a Mindset environment holds
Two environments inside one Mindset organisation. The connections are what make them different, because each points at different systems.
The connections are the important part. A finance connection in your Mindset Test environment holds the credentials for your test finance system. An agent built in Test cannot read a real invoice, cannot raise a real query, and cannot be made to by editing its instructions, because the credentials for the real system are not in that environment.
What your teams have today
Only one of the products your people build in gives them somewhere to build that is not live, and it is not one of the two most of them use.
Is there somewhere to build that is not live?
For the two that answer no, a Mindset Test environment is the first non-production place those teams have had.
How the work moves through them
Nobody moves tool. People keep building where they build today, and the working result comes into a Mindset Test environment first.
How the work moves through Mindset environments
Build where you build today. The result comes into a Mindset Test environment, then into Mindset Production once it holds up.
The agent is published back out to wherever people already work: the Mindset Hub for colleagues, an embedded element in your own product, or back into Claude over MCP. All three carry the same grant.