> ## Documentation Index > Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt > Use this file to discover all available pages before exploring further. # HPE Aruba Networking Central API > Read Aruba Central alerts, access points, switches, gateways, clients and site health, acknowledge alerts, reboot devices and move them between groups and sites, on Central or Classic Central The common use is a device-down or alert ticket: the agent finds the device in the customer's Aruba Central tenant, reads its status, its site's health and the alerts around it, writes what it found on the ticket, and acknowledges or clears the alert once the issue is handled. > [!NOTE] > > Automatically enabled when you configure HPE Aruba Networking Central permissions in your agent workflow. ## What It Does * Work in the ticket company's own Aruba Central tenant, from the company mapping * Read alerts and notifications, events, insights and audit logs; acknowledge, clear, defer or reprioritize alerts * Read access points, switches, gateways, stacks and swarms: status, ports, PoE, radios, uplinks, tunnels and trends * Read site and network health, topology and routing tables * Find a user's wireless or wired client, its connection and its roaming history * Move devices between configuration groups or device groups, and add devices to or remove them from sites * Reboot a device, blink its LEDs, bounce a port or its PoE, run a cable test, disconnect clients * Run ping, traceroute, show commands and other troubleshooting tests from a device * Read and change configuration, firmware, inventory, subscriptions, security and guest settings, users and alert rules Neo works with both platforms: **Central**, the current platform managed from HPE GreenLake, and **Classic Central**. Their paths differ, and the agent's skill uses the ones for your platform. ## Permission Groups | Group | Access levels | Covers | | - | - | - | | Alerts & Events | Disabled, Read Only, Read / Write | Alerts and notifications, insights, events, audit logs; acknowledge, clear, defer or reprioritize alerts | | Devices & Health | Disabled, Read Only, Read / Write | Access points, switches, gateways, stacks and swarms; site and network health, topology, routing, reports | | Clients | Disabled, Read Only, Read / Write | Wireless and wired clients, client match, the client deny list, GDPR exclusions | | Groups, Sites & Labels | Disabled, Read Only, Read / Write | Configuration groups, device groups, sites, site collections and labels, and the devices in them | | Device Actions & Troubleshooting | Disabled, Read Only, Read / Write | Reboot, locate, port and PoE bounce, cable test, client disconnect; ping, traceroute and show commands (these only read) | | Configuration | Disabled, Read Only, Read / Write | Templates and variables, WLANs, AP and switch settings, Central configuration profiles, SD-WAN, AirGroup and overlay services | | Firmware | Disabled, Read Only, Read / Write | Firmware versions, compliance and upgrades | | Inventory & Licensing | Disabled, Read Only, Read / Write | Device inventory, subscriptions and licences, device replacement | | Security, NAC & Guest Access | Disabled, Read Only, Read / Write | Rogue APs and intrusions, Cloud Auth and NAC registrations, guest portals and visitors | | MSP Tenants | Disabled, Read Only, Read / Write | Your tenants, their devices and users, assigning devices to a tenant | | Users & Administration | Disabled, Read Only, Read / Write | Users and roles, single sign-on, alert notification settings and rules, webhooks | | RF, Location & IoT | Disabled, Read Only, Read / Write | AirMatch and RF, floor plans, location and presence analytics, BLE beacons, IoT apps and gateways | ## Access Profiles | Profile | What runs on its own | What asks a technician | | - | - | - | | **Read Only** | Every read, troubleshooting tests included | No write is allowed | | **Helpdesk** | Every read | Every change in Alerts & Events, Clients and Device Actions & Troubleshooting (acknowledging an alert, a reboot, a port bounce); no other write is allowed | | **IT Admin** | Every read, and every change outside the three groups on the right and the Safety Controls | Every change in Security, NAC & Guest Access, MSP Tenants and Users & Administration, and the Safety Controls | | **Full Automation** | Every read and write outside the Safety Controls | The Safety Controls | ## Safety Controls | Control | Behavior | | - | - | | **The ticket's customer only** | On a run for a ticket, Neo sends a call only for the tenant the ticket's company is mapped to, and no MSP-level call | | **Always asks a technician** | Deleting a site, site collection or group; restoring a group's configuration backup; erasing a device's configuration or halting it; switching an account or group between monitor and managed mode; setting a user's or device admin's password; changing single sign-on; removing devices from the inventory; a firmware upgrade for every MSP customer; an AP ranging scan; and a whole-record update of a WLAN, MPSK, RADIUS or AAA server or profile, server group or SNMP record, whose approval says the update must carry every field, because a hidden field it leaves out may be cleared | | **Refused** | Deleting an MSP tenant; the token endpoints and webhook signing keys; the Classic to Central transition calls; report downloads and file uploads | | **Named records** | Acknowledging Classic notifications must name the notifications; a device command must be one the API reference lists | | **Secrets** | Passwords, passphrases, shared secrets, community strings and tokens are hidden in every answer | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.