Add supported asset
Your progress is saved automatically.
Your saved draft will remain available, but credential values cannot be recovered.
Your completed non-secret draft choices are saved. Credential values are never saved and must be entered again after sign-in.
Choose existing approved monitoring credentials or explicitly provision new access.
Use an existing credential profile · Inspect and provision accessUse temporary administrator access once so NEXXVU can identify this Proxmox system and prepare a least-privilege monitoring plan.
{% else %}Create a read-only NEXXVU monitoring identity, grant monitoring access, create its API token, and verify it works.
{{ plan.summary }}
{% if plan.reused %}The API token uses privilege separation. Effective access is the intersection of the dedicated user and token ACLs.
All proposed records are committed together after the checks below. Connection validation does not mean monitoring results already exist. Target-side provisioning already performed is shown below and is not rolled back by a database rollback.
{% endif %}Confirm the operator-facing identity, relationships, connection, saved credential reference and monitoring choices before the Asset is created.
{% if draft.data.provisioning_state == 'verified' %}Editing provisioning settings returns to inspection and requires a new plan, explicit approval, reconciliation and independent verification before this review is available again.
{% endif %} {% if proxmox_verification_commands %}Run these read-only listing and permission checks in an authorized Proxmox shell. They verify the exact NEXXVU user, role, ACL, token, privilege separation and effective permissions. They do not reveal the token secret and do not replace NEXXVU’s verification.
{% for command in proxmox_verification_commands %}{{ command }}{% if not loop.last %}
{% endif %}{% endfor %}Confirm user {{ proxmox_service_user }}, role {{ proxmox_role }}, token {{ proxmox_token_id }}, privilege separation enabled, and audit/read-only effective permissions.