--- title: "Projects & environments" canonical: "https://admiral.io/docs/get-started/projects-and-environments" description: "Create the project the walkthrough deploys into, and the dev and prod environments you deploy and promote between, each through your agent." --- # Projects & environments Now you create what Admiral deploys *into*: a [project](https://admiral.io/docs/concepts/projects-and-components.md) to own the work, and the two environments you'll deploy and promote between. Each environment deploys through the agent from step 1. ## 1. Create a project **CLI:** ```bash admiral project create demo ``` **Console:** Open **Projects**, choose **New project**, and name it `demo`. ## 2. Create dev and prod environments **CLI:** ```bash admiral env create demo/dev --agent demo admiral env create demo/prod --agent demo ``` **Console:** Inside the `demo` project, add two environments, `dev` and `prod`, and choose the `demo` agent for each. Each environment renders into its own namespace unless you name one with `--namespace`: here `demo-dev` and `demo-prod`. The agent creates the namespace on the first apply. > **Note:** An environment can require approvals before an apply runs, with `--approvals 1`, for example. Someone other than the changeset's author must then run `admiral changeset approve`. The walkthrough leaves approvals off, so you can finish it alone. Check what you made with `admiral env describe demo/dev`. It lists the environment's agent and namespace, and later the components it runs.