Proxmox VE clusters, security & access control EE, monitoring, maintenance, general settings and notification channels.
Configuration
Everything you set up once, before (or while) using the modules.
Administration
Section titled “Administration”Setup for the whole application. It requires admin privileges.
Required Proxmox VE permissions for each module: a quick reference for least-privilege setups.
Optional file for low-level overrides that have no UI control: database connection, password and lockout policies, login cookie, logging.
Modules
Section titled “Modules”Each module keeps its own settings, next to the module itself.
- Where: the gear button (Settings) in the header of the module page.
- Who: users with the Edit Settings permission of that module. Roles and permissions are managed in Security & Access Control EE.
- For which cluster: a module that works on one cluster saves its settings for each cluster, so open them with the right cluster selected. A module that works on all clusters saves them once. See Cluster scope.
| Modules with settings | Modules without |
|---|---|
| AI Server, AutoSnap, Backup Analytics, Bots, Diagnostics, Metrics Exporter, Node Protect, Replication Analytics, Update Manager, UPS Monitor EE | Dashboard, Resources, System Report, Portal EE, VM Performance EE, Workflow EE |
Some settings appear in several modules:
| Setting | What it is |
|---|---|
| Enabled | Marks the module as in use on that cluster. What it switches on depends on the module, and its page says so. |
| Enable scheduling | Runs the module on a schedule, written as a cron expression. |
| Max days logs | How many days of collected data the module keeps. |
| Max parallel requests | How many requests a scan sends at the same time. |
| Notifier | The notification channels the module sends its results to. |
You write the cron expression in the built-in editor, which shows a readable description and the next run. The schedule follows the time zone of the container (TZ).
The settings of each module, with their defaults, are in the Settings section of its page.
Personal
Section titled “Personal”Per-user preferences: every signed-in user can change their own.
Language, password, two-factor authentication EE, personal audit log EE, active sessions, theme.
Where settings live
Section titled “Where settings live”| Where | What |
|---|---|
| Database | All UI-driven settings: cluster credentials, users, roles, notifier channels, module options. They survive container updates. |
appsettings.extra.json |
Bootstrap configuration: database connection, log level, identity policies. Stored in /app/config/ (Docker volume, data/cv4pve-admin/config on the host) and read at startup. |
/app/data/ (Docker volume, data/cv4pve-admin/data on the host) |
Persistent application state: logs, images, translations, temp files. The PostgreSQL database is stored in a separate volume (data/postgres/data). |
.env and environment variables |
Container deployment settings: image tag, published port, database credentials, time zone (TZ), Watchtower token. See Installation Guide. |
