> ## Documentation Index > Fetch the complete documentation index at: https://docs.envzero.com/llms.txt > Use this file to discover all available pages before exploring further. # Force Remote Backend > Require all future Terraform environments in a project to use the env zero remote backend, making workspace name a mandatory field on environment creation. When `force env zero remote backend` is enabled, all future Terraform environments in the current project will be created with a [Remote Backend](/guides/admin-guide/remote-backend), which by default is not enabled. This policy can be enabled in Project Settings -> Policies Project Settings Policies page showing the Force env zero remote backend toggle The `Use env zero Remote Backend` checkbox will be checked and blocked for modification: Environment creation form showing Use env zero Remote Backend checkbox checked and locked Mandatory fields Please note that after enabling `Force env zero remote backend` feature, all newly created environments will require a workspace name to be added. (same applies for API calls.) ## Next steps * [Self-Hosted Remote State](/guides/admin-guide/remote-backend/self-hosted-remote-state) - Configure remote state storage in your own cloud account. * [State Migration](/guides/admin-guide/remote-backend/state-migration) - Move existing Terraform state into the env zero remote backend. * [Policies](/guides/policies-governance/policies) - Explore other project-level policy controls.