> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.method.security/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.method.security/_mcp/server.

# Create a new Environment

> Add and configure a new Environment through the Administration app or the onboarding workflow

This guide walks you through creating a new [Environment](/platform/core-platform/administration) in Method. Environments represent the networks, domains, and infrastructure you want to defend. You can create one from the Administration app or from the quick-action menu in the left navigation.

---

## Create an Environment

From the left sidebar, click the **Administration** icon, select the **Environments** tab, and click the **+** button in the top-right corner of the Environments panel.

![Administration app showing the Environments tab and add button](/_fern-files/_img/902449d64c0977bebdccc1a4fe5c22d6ebcecb02bebbc9a7f74f6155812c0e16.webp)

Alternatively, click the **lightning bolt** icon in the left sidebar and select **Create a new Environment**.

![Start something new menu showing the Create a new Environment option](/_fern-files/_img/ee3e1eb6fb8a2b5107cb583477d2349697ab831d95af7c1360e11eb88b0d4aeb.webp)

## Review existing Environments

Before adding a new Environment, you can review what already exists by browsing a searchable grid of every Environment in your organization. Type a name into the search bar to find a specific Environment, or click any card to view its details.

![Onboarding workflow with a grid of existing Environments](/_fern-files/_img/a1fd3860def0a34077d01c769b02dbc1e7ca5a0534bbb1785ded6e1904020ae4.webp)

## Define your Environment settings

Under the **Add a new Environment** section, fill in the following fields:

* **Environment name**: The name that identifies this Environment across the platform, including environment selectors, Finding filters, and Operation entry points.
* **Network type**: The connectivity model for this Environment. Choose **On-prem**, **Cloud**, or **Hybrid** to match your infrastructure.
* **Input data**: Add the starting inputs that seed your initial scans. You can provide **Critical Domains**, **CIDR Ranges**, or both. Type a value and click **Add** to include it, or click **Switch to CSV upload** to bulk-import entries from a file.

After configuring your Environment, you can preview the inputs you provided, add another Environment, or begin onboarding.

![Environment creation form showing name, network type, and critical domain fields](/_fern-files/_img/04b6e847c5833f312ef4b2c945a45cc0fcfea43f30d29615745d1664e3b36ae1.webp)

## Revisit your Environment details

To review or manage your Environment after creation, navigate to the Administration app and select it from the list. The detail page gives you a summary of the Environment's configuration, input data, scheduled scans, and any no-strike objects you have in place.

![Environment detail page for the newly created Environment](/_fern-files/_img/f0e3e86cd09d0b2c4ea4dbb3fa3b44b184ccdc5535055c07bc47f37e53104075.webp)

---

## Create a Tutorials Environment

If you are running through the Method guides, we recommend creating a dedicated Environment to keep your tutorial data separate from production data.

Follow the steps above and name your Environment `<yourname>-first-tutorial`. Use any domain you like as a Critical Domain (for example, `wayneindustries.xyz`). This Environment will serve as the target for subsequent guides, including [running your first Operation](/guides/operator/run-your-first-operation) and [creating a Task](/guides/automations/create-a-task).