> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Manage Projects

> View the projects list, navigate the project detail page, update project settings and policies, and delete projects in the Edge Intelligence Platform Console.

After creating projects, you can view their status, update their configuration, and delete them when they are no longer needed.

Open **Infrastructure > Fleet > Projects** to access project management.

## View Projects

The projects list displays each project's name, type, title, description, node count, tags, and the configuration status of its key policies.

Expand the **Summary** panel to view charts showing the distribution of projects by state, profile, and type.

You can filter the list by project name or tags using the search and filter controls.

Select any project in the list to open its detail page.

## Project Detail Page

The project detail page is organized into three tabs. The third tab depends on the project type.

| Tab | Shown for | Contents |
| - | - | - |
| **Overview** | All projects | Summary ribbon showing node, app instance, virtual network, volume, and policy counts; identity card with name, ID, title, description, type, and tags; EVE-OS version distribution; and project settings. |
| **Details** | All projects | Expanded read-only view of all project fields, including identity, ownership, configuration, and resource footprint. Deployment projects also show associated deployment records; Azure projects show the Azure IoT profile. |
| **Policies** | Standard and Azure IoT projects | All configured project policies, including node policy, virtual networks policy, edge apps policy, Edge View policy, and Edge Sync policy. |
| **Deployments** | Deployment projects | All deployment records held by the project. Deployment projects do not have a Policies tab, because their policies belong to individual deployment records rather than to the project. |

To view a log of project events, select the **View Events** button in the page header.

### View the deployment records

On a Deployment project, the **Deployments** tab shows one deployment record at a time.

If the project holds more than one deployment record, a **Select deployment** dropdown appears above the record details. Choose a record to view it. The dropdown is hidden when the project has only one deployment record, since there is nothing to choose between.

The selected record's summary shows its **Name**, **Deployment Tag**, **ID**, and **Version**.

Below the summary, the record's policies appear as a row of tabs: Edge Nodes Policy, Virtual Networks Policy, Volume Instances Policy, Edge Apps Policy, and Edge View Policy. Select a tab to view that policy's configuration. Policy types that the deployment does not use show **Not configured**.

The policy tabs are read-only. To change the policies a node receives, add a new deployment record as described in the following section.

### View the EVE-OS version distribution

The **Overview** tab includes an EVE-OS version distribution card that groups the project's nodes by the EVE-OS (Edge Virtualization Engine) version they report.

* Select any version row to open a list of the nodes running that version. The newest version is tagged **Latest**.
* Nodes that have not reported an EVE-OS version, for example a node that has not yet checked in, appear under an **Unknown version** row.
* When a project spans more than five versions, the remaining versions collapse into a single **+N other versions** row that opens a combined list of those nodes.

Select any node in the list to open its detail page.

## Update a Project

You can update a project's title, description, tags, and policies after creation. A project's name and type cannot be changed after creation.

### Update basic info

1. Open **Infrastructure > Fleet > Projects** and select the target project.
2. Select the **Configure** icon in the page header.
3. Update the **Title**, **Description**, or **Tags** as needed.
4. Select **Save**.

### Update policies on a Standard or Azure IoT project

1. Open **Infrastructure > Fleet > Projects** and select the target project.
2. Select the **Configure** icon in the page header.
3. Select the **Policies** section.
4. Select or clear checkboxes to add or remove policies.
5. Modify policy configuration fields as needed.
6. Select **Save**.

Policy updates are pushed to all nodes in the project the next time those nodes check in.

### Update policies on a Deployment project

A Deployment project has no **Policies** section in the Configure modal. Its policies belong to individual deployment records, so you change them by adding a deployment record.

1. Open **Infrastructure > Fleet > Projects** and select the target project.
2. Select the **Configure** icon in the page header.
3. Select **Deployment Profile > Deployments**.
4. Select **Add Deployment**.
5. Enter a **Deployment Tag Name**. If this is the project's first deployment record, also enter a **Deployment Name** and **Deployment Title**. On later records those two values carry over from the first record and are not requested again.
6. Select the checkbox next to each policy you want the deployment to carry: Edge Nodes Policy, Virtual Networks Policy, Edge Apps Policy, Volume Instances Policy, or Edge View Policy.
7. For each selected policy, select **Configure** and complete its fields. See [Configure Project Policies](https://zededa.mintlify.site/new-ui/infrastructure-services/projects/configure-project-policies.md).
8. Select **Add Deployment**.

Nodes tagged with the deployment tag receive the new policy set the next time they check in.

To remove a deployment record, select its checkbox in the **Deployments** section, open the actions menu, and select **Delete Deployment**. Deleting a deployment removes the application data associated with it on the edge node and in Edge Infrastructure Services, and the deployment cannot be restored.

#### Prefilled values on an existing project

On a project that already has a deployment record, the Add Deployment dialog does not open empty. It loads that deployment and prefills every policy the deployment already carries, so you are editing the project's existing policy set rather than building a new one:

* Each policy the deployment carries is already selected, and its configuration fields hold the current values. This includes the Edge Apps Policy, where the dialog also restores the app that each entry targets.
* The **Add Deployment** button is unavailable for a moment while the existing deployment loads. Wait for it to become available before you select it.
* Clear a policy's checkbox to drop that policy from the deployment. Leaving a prefilled policy untouched resubmits it unchanged.

A policy name is permanent. The **Name** field on the Edge Nodes Policy is read-only after the policy is first saved, and so is the **Name Prefix** field on each saved entry in the Edge Apps Policy. A policy or an entry that you add for the first time in this dialog stays editable until you save it. The **Title** field, target tags, and the remaining policy settings stay editable at all times.

## Delete a Project

A project must be empty before you can delete it. Edge Infrastructure Services refuses the delete, and the project stays in place, while any of the following still references the project:

* A node, network, deployment, application instance, virtual network, volume instance, or cluster.
* The project access list of a datastore, image, or edge application.

The console shows the refusal as an error. The message names the first blocker it finds, for example `One or more Device is still attached to Project. Delete Device(s) first.` or `One or more Deployments are still attached to Project. Delete Deployment(s) first.` The `Deployments` message also appears when the remaining blocker is an application instance, virtual network, volume instance, or cluster, so review all resource types in the project before you retry.

Policies attached to the project do not block the delete. They are deleted with the project.

### Delete a single project

1. Open **Infrastructure > Fleet > Projects** and select the target project.
2. Select the **Delete** icon in the page header.
3. Review the items that will be deleted.
4. Select **Delete** to confirm.

### Delete multiple projects

1. Select the checkboxes next to the target projects in the list view.
2. Open the **Actions** menu.
3. Select **Delete**.
4. Confirm the deletion.

## Next Steps

> [card] [Configure Project Policies](https://zededa.mintlify.site/new-ui/infrastructure-services/projects/configure-project-policies.md)
>
> Field-level detail on policy types.

> [card] [Onboard nodes](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/onboard-nodes.md)
>
> Assign nodes to a project.

> [card] [Node status and health](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/node-status-and-health.md)
>
> Monitor nodes after they join a project.

> [card] [Manage Projects With ZCLI](https://zededa.mintlify.site/zcli-reference/projects.md)
>
> Create, update, and delete projects and deployments from the command line.