Project settings

General

• Project name, slug (used in URLs), description and accent color.
• Unsaved changes wait in a Save/Reset bar until you commit or discard them.
• The whole page needs project.settings, which also lets holders edit names that a template rule would otherwise assign.

Infrastructure

• Enable the clusters the project may use. Enabling one turns on all its nodes that aren't offline; Rescan re-discovers nodes and storage.
• Switch individual hosts on or off. The load balancer only places new VMs on enabled hosts.
• Assign storage per cluster: VM disks, templates, ISO library and backup repository. Every live volume is listed with type, content and usage.
• VMID reuse blacklist: after a VM is deleted its VMID is blocked for a configurable number of days (0 means forever).

Import existing VMs

Adopt VMs that already exist on Proxmox, for example when moving from another portal, from a CSV or XLSX file (needs vm.create).

1. 1Choose Import existing VMs under Infrastructure and pick the file.
2. 2Check the preview of the first rows and the column mapping: match by VMID or by name, plus the owner column. The mapping is guessed from the headers.
3. 3Start the import and review the report.

• Proxmox is the source of truth: the file only supplies the owner. Name, sizing, node and status are read from the cluster, and rows whose VM isn't found fail.
• Owners are matched by email, directory account or display name. Unknown owners are skipped and reported, never guessed.
• VMs already in the portal are skipped, so the same file can be imported again after fixing users. A VMID that exists on several clusters is refused.

Quotas and defaults

• Quotas for vCPU, memory and disk show current usage; the bar warns at 75% and turns red at 90%.
• Defaults for new VMs: the cluster, network and VLAN, and template the wizard starts with.
• Per-template rules live on each template's Defaults tab.

Deployment: domain join

• Turn domain join on or off. When off, deployments only rename the machine.
• Domain (for example corp.example) and default OU; templates can override both.
• Delegated join account, for example CORP\svc-join. The password is write-only: stored encrypted and never shown again. Leaving it empty on save keeps the current one.
• The same account is used to remove a deleted VM's computer object from AD.

Danger zone

• Archive hides the project and freezes provisioning; running VMs keep running.
• Delete permanently removes the project with all its VMs, snapshots, backups, NICs, grants and settings, behind press-and-hold and a confirmation dialog.

Features on this page

• Project quotas
• VMID reuse blacklist
• VM import from CSV or XLSX