Skip to main content
The tool reaches your own Prism Central through the Nutanix v4 API, signed in with the API key of the service account you save in Neo, so each call is limited twice: by that service account’s roles in Prism Central and by the agent’s permission groups below.
Automatically enabled when you configure Nutanix permissions in your agent workflow. No manual toggle needed.

​
What It Does

  • Find a VM by name, DNS name or the BIOS UUID an RMM shows, or a client’s VMs by SP Central tenant, project, category, cluster or naming prefix
  • Read the vCPUs, memory and disks a VM is given, and its CPU, memory and storage use over a period; add these up for a client
  • Read an SP Central tenant’s CPU, memory and storage allocation and its projects
  • Add or remove vCPUs and memory, add a disk or grow one, and follow the change’s task to the end
  • Power a VM on, off or restart it, clone it, deploy one from a template, take and restore recovery points, and tag it with categories
  • Read cluster and host load, storage container free space, subnets, open alerts, events and audits; acknowledge and resolve alerts
  • Manage images and templates, clusters and hosts, storage, networking, network security policies, data protection, upgrades and licensing, users and roles, and SP Central tenants, with the access and approvals you choose
The agent calls the v4 API through the Vendor API tool, with nutanix as the vendor id. Sandbox scripts can call Nutanix too, under the same permissions. Neo adds the ETag a change needs from the entity the agent read, and a fresh request id to every change.

​
Permission Groups

Every group can be Disabled, Read Only or Read/Write. Neo never sends these calls: a batch of API calls in one; a VM console token; creating an API key or an object store key, reading a claim token’s secret, a VPN device’s configuration or the cluster’s encryption key backup; destroying a cluster; unregistering Prism Central or restoring it from a backup; and the calls that upload or download a file, such as an image download, a report file or a certificate upload. Neo removes the fields Nutanix keeps credentials in from every answer.

​
Access Profiles

Every group Read Only. The agent reads, and never changes anything.
Alerts, Events and Reports and Categories and Tasks are Read/Write without approval. Virtual Machines is Read/Write with technician approval. Everything else is Read Only.
Every group Read/Write. Network Security Policies, Users, Roles and Access, Upgrades and Licensing, Prism Central, Security and Encryption, and Tenants require technician approval, and so do the changes below.
Every group Read/Write without approval, except the changes below, which still require technician approval.

​
Safety Controls

These require technician approval under every access profile, whatever the group’s own approval setting:
  • Deleting a VM, a VM disk, a recovery point, an image, OVA or template, a storage container, a volume group or its disk, a physical disk, a file share, an object store, a node or an SP Central tenant, removing a node from a cluster, and clearing a container’s reserved space.
  • Uninstalling guest tools from a VM, and unregistering the vCenter extension.
  • Any change in Users, Roles and Access, and in Prism Central, Security and Encryption.
  • Any change to alert policies or alert email. Acknowledging or resolving an alert does not ask on its own.
  • Any change that stores a credential.