# How to Create a Project in TestOwl

:::lead
A project is your team's workspace in TestOwl. Everything you build—tests, flows, environments, variables, secrets, run history, and team members—belongs to a project.
:::

Think of a project as a container for a single application or product that you want to test. Each project is completely independent, making it easy to organise different applications, teams, or customers without sharing data between them.

## When should you create a new project?

In most cases, create **one project per application or product**.

For example:

- One project for your customer-facing website.
- One project for your admin portal.
- One project for your mobile web application.
- One project for each client if you're an agency or consultancy.

Keeping related tests together makes it easier to manage environments, test data, team members, and execution history.

:::callout{title="Recommended"}
Avoid creating separate projects for individual features or modules. Instead, organise related functionality using **Test Suites**, **Test Cases**, and **Flows** within the same project.
:::

## Create a project

:::info{title="Your first project"}
When you sign in for the first time, [onboarding](/docs/getting-started/account-and-authentication#first-time-onboarding) already creates your first project for you, so you'll land on the dashboard with a project ready to go. Use the steps below to create any **additional** projects.
:::

Creating a new project only takes a few seconds.

1. Open the **Project Switcher**.
2. Enter a project name.
3. Click the **+** icon.
4. You're ready to [record your first test](/docs/getting-started/quickstart).

You can rename your project later from **Settings → Manage Project**.

:::info{title="Sample Demo Project"}
Every account includes a read-only **Sample Demo Project** with example test suites, flows, environments, and run history. It's a great place to explore TestOwl before creating your own project. Changes you make there aren't saved, and recording is turned off.
:::

## What belongs to a project?

Each project contains its own resources, including:

- **Team members** and their roles.
  - Learn more about [Roles & Members](/docs/team-and-account/project-roles) and [Inviting Team Members](/docs/team-and-account/inviting-members).

- **Test Suites**, **Test Cases**, and **Flows** used to build and organise your automated tests.
  - See [Test Suites](/docs/building-tests/test-suites), [Test Cases](/docs/building-tests/test-cases), and [Flows](/docs/building-tests/flows).

- **Environments** that define where and how your tests execute.
  - See [Environments](/docs/environments/overview).

- **Variables** and **Secrets** used to store reusable configuration and sensitive information.
  - See [Variables](/docs/data/variables) and [Secrets](/docs/data/secrets).

- **Schedules** that run your tests automatically.
  - See [Scheduling Runs](/docs/running-and-results/schedules).

- **Run History** and **Reports** for every test execution.
  - See [Run History](/docs/running-and-results/run-history) and [Reports](/docs/running-and-results/reports).

- A **plan** and **billing** for the project.
  - See [Plans & Usage](/docs/team-and-account/plans-and-usage).

## Project isolation

Projects are completely isolated from one another.

Resources created in one project are **not shared** with any other project, including:

- Test Suites
- Test Cases
- Flows
- Environments
- Variables
- Secrets
- Schedules
- Run History
- Reports
- Team members

This isolation helps keep applications, customers, and teams organised.

## Deleting a project

:::alert{title="Warning"}
Only **Project Owners** can delete a project, from **Settings → Manage Project**. You'll be asked to type the project's name to confirm.

Deleting a project permanently removes everything inside it, including test suites, test cases, flows, environments, variables, secrets, run history, and reports.

This action cannot be undone.
:::

## Plan limits

Every project runs on its own plan. New projects start on a free **Trial** with every feature unlocked, and limits such as team members, environments, schedules, and test executions depend on the plan. See [Plans & Usage](/docs/team-and-account/plans-and-usage).

For more information, see [Plans & Usage](/docs/team-and-account/plans-and-usage).

## Next steps

::::cardgrid
:::card{title="Navigating TestOwl" href="/docs/getting-started/navigating-testowl"}
Take a tour of the interface and learn where everything lives.
:::

:::card{title="Quickstart" href="/docs/getting-started/quickstart"}
Create your first automated test in just a few minutes.
:::

:::card{title="Inviting Team Members" href="/docs/team-and-account/inviting-members"}
Collaborate with your team by inviting additional members.
:::

:::card{title="Environments" href="/docs/environments/overview"}
Configure where and how your automated tests will run.
:::
::::