# Create and manage projects

Source: https://docs.qualflare.com/docs/administration/projects · Last updated: 2026-10-27

Create a Qualflare project, set its name, identifier and description, give people access, find each settings tab and delete a project safely.

To create a project in Qualflare, click **Create Project** on the workspace **Projects** page; you need the Editor role or higher in the workspace, and your plan sets how many projects the workspace can hold (Starter allows 1).

## How projects work

A [project](https://docs.qualflare.com/docs/reference/glossary#project) belongs to exactly one workspace and holds its own [test cases](https://docs.qualflare.com/docs/test-management/test-cases), [test suites](https://docs.qualflare.com/docs/test-management/test-suites), launches and results. Projects are where you create and organize test cases, run launches (manual or automated), track defects, and view results and analytics. For where projects sit in the full hierarchy, see the [Workspace hierarchy](https://docs.qualflare.com/docs/administration/workspaces#workspace-hierarchy) diagram.

Common ways to organize projects:

* **By Product**: One project per application or service
* **By Component**: Frontend, Backend, API, Mobile as separate projects
* **By Team**: Each QA team has their own project

Use environments, not separate projects, for Dev, Staging, and Production. Every new project starts with Development, Staging, Production, and QA environments, so one project keeps a single history that you can compare per environment. See [Environments](https://docs.qualflare.com/docs/runs/environments).

## Before you begin

Requires the Editor role or higher in the workspace.

Creating a project needs the Editor role or higher in the workspace, so Viewers and Guests can't create projects (Guests don't see the button). Your plan sets how many projects a workspace can have. See [Limits](https://docs.qualflare.com/docs/administration/plans#limits) for every plan.

## Create a project

Your first project is created during sign-up. To add another:

### Step 1: Open Projects

Open **Projects** in the workspace sidebar.

### Step 2: Open the Create Project dialog

Click **Create Project**.

### Step 3: Fill in the project details

* **Project Name**
* **Project Identifier**: the project's URL slug. Qualflare fills it in from the name. Edit it now if you want to: the dialog says "You cannot change it later."
* **Project Description**: required, 3 to 2,048 characters. Qualflare's AI features use it.
* **Project Domain** and **Platform**

### Step 4: Create the project

Click **Create Project**.

*Figure: The Project Identifier becomes the project's URL and can't be changed later.*

**What a new project includes:**

* You get the Owner role in it.
* Four environments: Development, Staging, Production and QA.
* Until its first launch arrives, the project's **Overview** shows a setup guide with the steps to upload results. Right after you create the project, the guide shows an [access token](https://docs.qualflare.com/docs/api/access-tokens) once; on a later visit it offers **Generate access token** instead.

On the Open Source plan, every project is linked to a public GitHub repository, which you pick in the same dialog. The project name and identifier come from the repository, so you can't edit them. See [Open Source](https://docs.qualflare.com/docs/open-source) and [Activating the Open Source plan](https://docs.qualflare.com/docs/open-source/activating).

## Configure a project

Requires the Editor role or higher in the workspace.

### Step 1: Open the project's General settings

Navigate to the project, click **Settings** in the left sidebar, and stay on the **General** tab.

### Step 2: Set the project basics

* **Project Name**: the display name shown in selectors and reports
* **Description**: required. Qualflare uses it to personalize the project's [AI features](https://docs.qualflare.com/docs/ai)
* **Project Domain** and **Platform**

### Step 3: Save the project

Click **Save Project**.

The **Project Identifier** is shown read-only. It's set when the project is created and can't be changed. Saving these fields needs a workspace role of Editor or higher. In the web app today, the fields also need the Editor role or higher in this project.

Access tokens belong to one project, so the CLI doesn't use the Project Identifier. See [Using Tokens with the CLI](https://docs.qualflare.com/docs/api/access-tokens#using-tokens-with-the-cli).

Each settings tab controls one area:

| Tab               | What it controls                                                                                       |
| ----------------- | ------------------------------------------------------------------------------------------------------ |
| **General**       | Name, description, domain and platform, the public report (Open Source plan), and **Delete Project**   |
| **Notifications** | Your own email switch, project-wide email notifications, and in-app insight alerts                     |
| **AI Features**   | Turns AI features on or off for this project                                                           |
| **Quality**       | Flaky test detection thresholds and quality targets                                                    |
| **Environments**  | The project's environments                                                                             |
| **Webhooks**      | HTTP callbacks for this project. See [Webhooks](https://docs.qualflare.com/docs/integrations/webhooks) |
| **Users**         | Invitations and project roles                                                                          |
| **Access Tokens** | Tokens for the CLI, scripts, and AI coding agents                                                      |

See [Project Settings](https://docs.qualflare.com/docs/administration/project-settings) for every field.

## Give people access

People get into a project by invitation: see [Invite people to a project](https://docs.qualflare.com/docs/administration/users#invite-people-to-a-project), and to keep an outside collaborator to a few projects, [Limit someone to specific projects](https://docs.qualflare.com/docs/administration/users#limit-someone-to-specific-projects). A person's access in a project is the higher of their project role and their workspace role (see [How workspace and project roles combine](https://docs.qualflare.com/docs/administration/roles-permissions#workspace-and-project-roles)).

Projects have no visibility setting. Access comes from two roles:

* Your **workspace role** applies in every project in the workspace
* Your **project role** comes from creating the project (Owner) or accepting an invitation to it (Viewer). It can raise your access in that project, never lower it
* People invited to a project who weren't in the workspace yet join it as **Guests**, and see only the projects they were invited to

## Delete a project

Deleting is the only way to remove a project, because projects can't be archived.

> **Caution:** Deleting a project removes it and every test case, suite, launch, defect, and milestone in it, for everyone. You can't undo it or restore the project in the app.

Requires the Owner role in the workspace.

To delete a project, you need the Owner role in the workspace and in the project. The **Delete Project** card shows only to the project's Owner (the person who created it), and the deletion succeeds only for the workspace Owner.

### Step 1: Go to the General tab

Go to **Project Settings** > **General**.

### Step 2: Open the Delete Project card

Scroll to the **Delete Project** card and click **Delete Project**.

### Step 3: Confirm with the project identifier

Type the project identifier to confirm, then click **Delete Project**.

## Verify

A new project appears on the workspace **Projects** page, and its pages are at `app.qualflare.com/project/<project-identifier>`.

## Troubleshoot

* **Create Project is missing**: you're a Guest in the workspace. The button is hidden only for Guests. Ask a workspace Maintainer or Owner to promote you to Editor.
* **Create Project is there, but creating fails**: you're a Viewer in the workspace. The app shows the button, but creating a project needs the Editor role or higher in the workspace. Ask a workspace Maintainer or Owner to promote you to Editor.
* **Creating fails at your plan's project limit**: projects can't be archived, so delete a project or change plans. See [Billing and Subscription](https://docs.qualflare.com/docs/administration/workspaces#billing-and-subscription).
* **The Delete Project card is missing**: only the project's Owner sees it, and only a workspace Owner's deletion succeeds.

## Next steps

* [Invite and manage users](https://docs.qualflare.com/docs/administration/users): invite people and set their roles
* [Project Settings](https://docs.qualflare.com/docs/administration/project-settings): every tab and setting of a project
* [Project teams](https://docs.qualflare.com/docs/administration/teams): group project members and route work to them
* [Collect Test Results](https://docs.qualflare.com/docs/cli/collect): upload your first results with `qf <identifier> collect`