> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/feature-management-experimentation/management-and-administration/projects.md).

# Projects

Projects let you organize and manage feature flags, experiments, metrics, and more for a specific team, business unit, or application in Harness FME. Harness recommends creating one [project](/harness-ai/new-to-harness-platform/overview.md#projects) per team, business unit, or independently managed application domain.

* Use a single project when teams need to share feature flags, metrics, environments, or visibility across services.
* Use separate projects when teams require isolated RBAC, independent release cadences, or strict separation of feature flag and experimentation data.

Projects in Harness FME are hard partitions for feature flag and experimentation data. Related flags (such as parent-child or flag prerequisites) and metrics that rely on the same event streams must exist within the same project. If you only need lightweight organization within a shared domain, consider using naming conventions and tags instead of creating separate projects.

When you first create your account, Harness FME provides a default project named `Default`. The `Default` project includes two [environments](/feature-management-experimentation/management-and-administration/environments.md) and one [traffic type](/feature-management-experimentation/management-and-administration/traffic-types.md).

```mermaid
flowchart TB
    Account --> Organization --> Projects

    Projects --> Environments
    Projects --> Feature_Flags[Feature Flags]
    Projects --> Segments
    Projects --> Metrics
    Projects --> Event_Types[Event Types]
    Projects --> Traffic_Types[Traffic Types]

    Environments --> SDK_API_Keys[SDK API Keys]
```

<br>

You can rename and edit the default environments and traffic type, and create additional resources as needed. Projects contain and scope the following resources:

* [Feature flags](/feature-management-experimentation/use-fme/feature-management/setup/create-a-feature-flag.md)
* [Segments](/feature-management-experimentation/use-fme/feature-management/targeting/segments.md)
* [Metrics](/feature-management-experimentation/use-fme/release-monitoring/metrics/index.md)
* [Event types](/feature-management-experimentation/use-fme/release-monitoring/events/index.md)
* [API keys](/feature-management-experimentation/management-and-administration/api-keys.md)

### Create a project <a href="#create-a-project" id="create-a-project"></a>

Project creation in Harness FME uses the Harness platform [project workflow](/harness-ai/new-to-harness-platform/get-started.md#create-a-project). After creating a project, return to **FME Settings** to configure FME-specific options.

To create a project:

1. From the FME navigation menu, click **FME Settings** and select **Projects**.
2. Click **Create project** at the top right.

   ![](/files/Vaf1Zatn3jFZ2RCNkYUY)

   This opens the **Projects** page under **FME Settings** in the FME navigation menu.

   ![](/files/WSKpSbB4BkpMtzCFWj6a)
3. Click **+ New Project**.
4. Complete the following details:

   * Enter a name for the project.
   * Select a color option for the project.
   * Optionally, enter a description and add tags.

   ![](/files/H8ICjRwjVD7IsfmHr4fB)
5. Click **Save and Continue**.
6. Optionally, invite people to collaborate in the project by selecting a role from the dropdown menu (like `FME Manager`) and adding collaborators in your organization by email address.

   ![](/files/BIl9QUScVGWwMtXUThK9)
7. Click **Save and Continue**.

   ![](/files/nUrp8Jbjs5s1bpDFR3p2)
8. Next, click **FME Settings**.

   ![](/files/xYxpq7Fxg1YP1XRv5bQf)
9. Click **View** under **Actions** on the project you created (for example, `Documentation`).

   ![](/files/g7ovbKVc7GTisR74g0IV)
10. Click on the **Actions** dropdown menu and select **Edit project**.

    ![](/files/KjX4luCC9rFLojCzJq62)
11. Select the **Required title and comments comments** toggle to enable requiring titles and comments for feature flags, segments, and metric changes.

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can update this setting at any time by clicking <strong>Actions</strong> > <strong>Edit project</strong> on the top right corner in <strong>Project Settings</strong>.</p></div>
12. Click **Save**.

### Manage projects <a href="#manage-projects" id="manage-projects"></a>

You can manage projects in **FME Settings** and the **Projects** page.

#### Configure project settings <a href="#configure-project-settings" id="configure-project-settings"></a>

In **FME Settings**, you can configure whether project changes require [titles and comments](/feature-management-experimentation/management-and-administration/audit-logs.md#titles-and-comments-in-changes) for auditability and change tracking.

![](/files/u4N0zT5TyEgNvJKAz2VF)

To configure project settings in Harness FME:

1. Navigate to **FME Settings** > **Projects**.
2. Click **View** for the project you want to configure.
3. Open the **Actions** dropdown menu and select **Edit project**.
4. In the **Edit project** dialog, enable or disable **Require title and comments for feature flag, segment, and metric changes**.
5. Click **Save**.

When enabled, users must provide a title and comment when modifying feature flags, segments, or metrics within the project. This can help improve change tracking and audit visibility across teams.

#### Delete a project <a href="#delete-a-project" id="delete-a-project"></a>

{% hint style="danger" %}
**DELETE FME RESOURCES BEFORE DELETING THE PROJECT**

Deleting a Harness project removes the associated Harness module resources within that project. However, Feature Management & Experimentation (FME) resources are not automatically deleted.

Before deleting a project, manually remove associated FME resources such as feature flags, segments, metrics, environments, and traffic types.
{% endhint %}

![](/files/OL0UGLJSnSSzgV6A2DDG)

To delete a project:

1. Navigate to **FME Settings** > **Projects**.
2. Click **View** for the project you want to delete.
3. Open the **Actions** dropdown menu and select **Delete project**.

   This redirects you to the broader Harness **Projects** management page for your organization.
4. Find the project, click the kebab menu (⋮), and select **Delete**.
5. In the **Delete Project** dialog, select **Yes, I want to delete this project**.

<details>

<summary>Still using `app.split.io`?</summary>

**Setting project permissions**

You can set view permissions to your projects or projects you have administrator rights to and any objects within the project. This allows you more granular control over which users, groups, and API keys can access the objects in projects to support access requirements within an account.

These objects include feature flags, segments, metrics, traffic types, and environments. This also allows you to determine who can see if a certain project exists.

Each Split project has a project permissions setting which you can use to restrict access to that project to specific users, groups, or API keys. If a user, group, or API key is not granted access to a restricted project, they cannot see the project name nor determine whether that project exists.

Project view restrictions can be used to protect sensitive (i.e., confidential) projects, or to improve user experience by showing a small number of relevant projects to each user.

**Viewing or updating project permissions**

An Admin can view or edit a project's permissions by following these steps:

1. Navigate to **Admin settings**.
2. On the **Projects** page, click the **View** link for a project.
3. Click the **Actions** button on the top left and select **Edit project**. The **Edit project** pane will appear.
4. On the **Edit project** pane, you can view project permissions. You can also restrict access to the project to some users, groups, and Admin API Keys.

To manage project-level settings:

1. Click **Actions** > **Edit project** in the top right corner of the **Projects** page.
2. In the **Edit project** pane, enable the **Require comments** toggle to enforce titles and comments for changes to feature flags, segments, and metrics.

   ![](/files/ZlRsiZDnwYc5eUxR85kg)
3. In the **Project permissions** section, optionally select the desired control access from the following options:
   * **Anyone has access**. Allows anyone to have access to this particular project.
   * **Restrict who can access**. Allows you to select which users, groups, and admin API keys have access to a particular project.
4. Click **Save**.

**Editing a project**

When you are viewing a project, you can edit a project by doing the following:

1. From the left navigation, click on the **profile button** at the bottom.
2. Click **Admin settings**, then **Projects**. A list of projects appears.
3. On the selected project you want to edit, click **View** in the **Actions** column.
4. Click the **Actions** button and then **Edit project** from the menu list. The Edit project page appears.

   ![](/files/zKZQLeCikh8XR0PnciEW)
5. In the **Name** field, optionally change the name.
6. Enable the **Require comments** toggle to enforce titles and comments for changes to feature flags, segments, and metric.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE</strong></p><p>When you check this box, it affects the approval flows.</p></div>
7. In the **Project permissions** section, optionally select the desired control access from the following options:
   * **Anyone has access**. Allows anyone to have access to this particular project.
   * **Restrict who can access**. Allows you to select which users, groups, and admin API keys have access to a particular project.
8. Click **Save** to save your changes. The changes appear in the admin audit logs.

**Viewing projects**

To view projects, do the following:

1. From the left navigation, click on the **profile button** at the bottom.
2. Click **Admin settings**, then **Projects**. A list of projects appears.
3. Select **View** on the desired project. From here, you can see the environment name, ID, type of project it is, permissions setting, and data export permission settings.

   ![](/files/2HO7QGK75ksjdc4oVjlv)

**Requesting access to projects**

If you have no access to a project, you need to request access from the administrator of that project.

**Navigating between projects**

You can navigate between projects by doing the following:

1. From the left navigation, click on the **profile button** at the top.
2. **Search or select the project** you would like to switch to. You can see the environments, feature flags, segments, and metrics under that project.

**Managing your projects**

To manage your projects, go to the **projects** tab in your **Admin Settings** page. On this page you can:

* See a list of all your existing projects.
* Manage the [environments](/feature-management-experimentation/management-and-administration/environments.md) and [traffic types](/feature-management-experimentation/management-and-administration/traffic-types.md) in a project by clicking **View** in the Actions column for selected projects.

**Deleting a project**

To delete a project, follow these steps:

* Make sure all feature flags, segments, and metrics are deleted from the project for all environments.
* To delete a feature flag, delete all the definitions from its environments.

  ![](/files/DeA6pk65r66XFwkkXz1k)
* Then, delete the feature flag.

  ![](/files/dkt2jhE99MEcyeHb3K9D)
* To delete a segment, first select all its keys.

  ![](/files/Wy4TjmE2rOib5sZgMKMq)
* Then, delete the keys.

  ![](/files/HbsEOW0qLjISy3m0NVPw)
* Then, delete the segment definition and repeat these steps for all environments.

  ![](/files/pC5a2Rm0OZEZjpjPxrrG)
* Finally, delete the segment.

  ![](/files/LXLNKJc5RmApdWNNARyt)
* To delete metrics, click on the upper top right (...) icon to delete it.

  ![](/files/FtieCO4lv6gKd4N5I3BT)
* In the Admin page, under the **API keys** page, Make sure all Admin API and SDK keys are revoked for the project environments. For example the screenshot below shows the SDK API key for the "default" project.

  ![](/files/PiXeBI1a58TFO9ErAHoX)
* In Admin settings, in the left menu, click **Projects**.
* In the list of available projects, click the **View** link of the project you want to delete.

  ![](/files/v651fAY1XKanmVzoqqfn)
* You will see a list of environments for the selected project, now you can delete each environment using the **Delete** link.
* The user interface will allow you to delete all environments except the last one, as each project is required to have at least one environment.
* Click the **Actions** button in the top right corner and choose the Delete project option, which will allow you to delete it.

  ![](/files/xTikXmkoHCERxs6uiGwQ)

</details>