> ## 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. # Projects Overview > Understand projects in Edge Infrastructure Services: what they are, the two project types, and how they relate to node management. A project is a logical grouping of nodes and the policies that govern them. When a node joins a project, the policies defined in that project are automatically applied: virtual networks, edge app deployments, volume instances, attestation requirements, and more. This lets you manage large fleets of nodes consistently without configuring each node individually. In the Edge Intelligence Platform Console, open **Infrastructure > Fleet > Projects** to view, create, and manage your projects. ## Before You Start | Requirement | Why it matters | | - | - | | SysManager or SysAdmin role. See [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md). | Required to create or modify projects. | | Enterprise configured | Every project belongs to a single enterprise. Your enterprise includes one empty project when it is first created. | | Policies planned in advance | Policies are applied to nodes automatically when they join the project. Plan your network, app, volume, and attestation requirements before creating the project. | | Nodes to assign (optional) | You can create a project before onboarding nodes. Nodes are assigned to a project during or after onboarding. | The maximum number of projects you can create is controlled by your enterprise entitlements. ## Project Types and Profiles Selecting the right project type determines which policies are available and how deployments are structured. | | Standard | Deployment | | - | - | - | | **Profile options** | Regular or Azure | Regular only | | **Best for** | Simpler environments with a single edge app per node | Complex environments with multiple edge apps across a fleet (tiered deployments) | | **Node Policy** | Yes | Yes | | **Virtual Networks Policy** | Yes | Yes | | **Edge Apps Policy** | Yes | Yes | | **Edge View Policy** | Yes | Yes | | **Edge Sync Policy** | Yes | No | | **Volume Instance Policy** | No | Yes | The policy sets differ because the two types store their policies in different places. A Standard project holds its policies on the project itself, so you configure them once and every node that joins the project receives them. A Deployment project holds its policies on each deployment record, so a single project can carry several policy sets and a node receives the one whose tag it matches. Use **Standard** for simpler setups, including Azure IoT Hub integrations. Use **Deployment** for tiered deployments where multiple edge apps must roll out to a fleet. For Azure IoT Hub setup and configuration, see [Azure Integration](https://zededa.mintlify.site/new-ui/infrastructure-services/integrations-and-automation/azure-iot-hub.md). ## Zero-Touch Deployments Zero-Touch Deployments (ZTD) is the mechanism that makes project policies act automatically on your nodes. When you onboard a new node and assign it to a project, the tags on that node are matched to the deployment tags defined in the project. Matching policies and applications are applied to the node automatically, without further manual configuration. ZTD is the primary reason to use the **Deployment** project type. In a Deployment project, you define one or more deployment configurations, each with a set of tags. When a node's tags match a deployment's tags, the deployment's network configurations, volume instances, and applications are applied to that node. To update which deployment applies to a node, change the node's tags to match the target deployment. Edge Infrastructure Services handles the transition automatically. ZTD also supports versioned rollouts. A project can hold up to 100 deployment versions. To roll back, update the node's deployment tag to match the tag of the previous deployment version. To set up the policies that ZTD applies to matching nodes, see [Configure Project Policies](https://zededa.mintlify.site/new-ui/infrastructure-services/projects/configure-project-policies.md). ## Tagging Tags are key-value pairs you assign to resources in Edge Infrastructure Services. The key and value are both strings you define, for example `env:production`, `region:emea`, or `tie-breaker:true`. Tags let you classify, filter, and automate across your infrastructure without changing how resources are configured. Tags are used throughout the project and deployment system: | Where tags are used | What they do | | - | - | | Nodes | Categorize nodes by geography, hardware, role, or environment. Used as targets for deployment and policy matching. | | Project deployments | Define which nodes receive a specific deployment's policies and applications. Nodes whose tags match the deployment tags receive that deployment automatically. | | Edge app policies | Specify which nodes receive a particular application deployment. | | Virtual network policies | Determine which nodes receive a specific network configuration. | | Clusters | Designate a node as a tie-breaker with `tie-breaker:true`. Required before creating a two-node HA cluster. | Consistent use of tags across your fleet reduces manual configuration and makes large deployments manageable. Plan your tagging scheme before creating projects and deployments so that policy assignments work correctly when nodes join. See [Tagging](https://zededa.mintlify.site/new-ui/start/tagging.md). ## In This Section * [Create a Project](https://zededa.mintlify.site/new-ui/infrastructure-services/projects/create-a-project.md): Step through the creation wizard to define project details, deployments, and settings. * [Configure Project Policies](https://zededa.mintlify.site/new-ui/infrastructure-services/projects/configure-project-policies.md): Configure the node, virtual networks, edge app, Edge View, and Edge Sync policies that govern nodes in the project. * [Manage Projects](https://zededa.mintlify.site/new-ui/infrastructure-services/projects/manage-projects.md): View the project list, navigate the detail page, update project settings, and delete projects.