Devices
Monitor endpoint connections, posture, and lifecycle.
Network → Devices lists every enrolled endpoint with its connection state, posture evidence and platform. Use it to confirm a device is connected, to see why it is not, and to archive, block, restore or revoke it.

Connection and posture are separate columns: a device can be Online and Non-compliant at the same time, as build-runner-02 is here.
Before you start#
- Reading the inventory needs
devices:view. Add Device needsdevices:create(owners, admins and users by default). Edit device needsdevices:update. Archive, block, restore, uninstall token and revoke all needdevices:revoke(owners and admins). - Agents ship for Linux, Windows and macOS (Apple Silicon and Intel). iOS and Android are marked Soon in the console and are not yet available.
- Connection and posture are separate facts. Online says the agent is heartbeating; Compliant says the latest posture check passed and is fresh.
Enroll a device#
- Click Add Device.
- Under Select Platform choose Linux, Windows or macOS.
- Under Install Agent copy the Linux install command, or use Download for Windows, Download for macOS (Apple Silicon) or Download for macOS (Intel). Linux packages are GPG signed and update through
apt upgradeordnf upgrade. - Under Authenticate: on Linux run the shown login command, then visit the URL and enter the device code. On Windows and macOS open the PulseHA app, click Continue in Browser and approve the device for your organization.
See Install the agent and Authorize a device for the full flow.
Read the inventory#
Filter with All, Connected, Disconnected, Compliant, Non-compliant, Pending, Blocked, Archived or Revoked. Search matches name, hostname, owner email or device ID. The list refreshes every 30 seconds.
| Column | Meaning |
|---|---|
| Device | Display name, with the owner’s email or description underneath |
| Connection | Connection chip and last-seen time |
| Posture | Posture chip and when it was last checked |
| Address | Tunnel IP |
| Platform | OS and agent version |
Connection labels:
| Label | Meaning |
|---|---|
| Online | Heartbeat within 4 minutes and the agent has not reported its tunnel down |
| Tunnel down | Heartbeat within 4 minutes but the agent reports the tunnel is not up |
| Recently seen | Last heartbeat between 4 and 10 minutes ago |
| Offline | Older than 10 minutes, or the agent reported disconnected |
| Never connected | No heartbeat recorded |
| Pending, Blocked, Archived, Revoked | Lifecycle states set by an operator or by enrollment |
Connected includes Online and Recently seen. Disconnected includes Offline and Tunnel down.
Posture labels are Compliant, Non-compliant, Stale and Unknown. A check older than 10 minutes, or a device whose heartbeat is older than 10 minutes, is Stale even if its last result was compliant. A known failure stays Non-compliant. Unknown means no result exists.
Inspect a device#
Click a row to open the drawer (?device=<id>). Tabs:

The Overview tab shows connection tiles, then platform, version, tunnel IP, external address, public key and the gateway the device is using.
- Overview: Connection, Data Received, Data Sent and Last Seen tiles, then Platform, Version, Hostname, Tunnel IP, External Address, Public Key, Gateway, NAT Type, Location, Last Seen and Created. If Orbit placed this device, an Orbit Egress section shows Egress region, Placed by (a routing rule or Automatic) and Status (Converged, Pending or Degraded).
- Performance: metrics over 24h, 7d or 30d.
- Posture: Effective posture policy (needs
policies:view) with Compliant, Non-compliant, Not covered or Unknown, the policy mode and configured action, then Last recorded status, Trust Score, Last Check and any failing agent checks with remediation hints. - Activity: device events, filterable by event type and by Info, Warning or Error.

The Posture tab names the effective policy, the last recorded status and trust score, and lists each check with its result.
Change a device’s lifecycle#
The drawer menu offers Edit Device, Copy Public Key, Archive Device, Block Device, Restore Device, Generate Uninstall Token and Revoke Device. The same actions sit in the Danger Zone of the edit page.
| Action | Effect |
|---|---|
| Archive | Marks the device dormant. Gateways are told to drop its peer. Reversible with Restore |
| Block | Disconnects the device immediately. Meant for lost or stolen devices. Reversible with Restore |
| Restore | Returns a blocked or archived device to inactive so it can reconnect |
| Generate Uninstall Token | Produces a one-time token and the command pulsectl uninstall --token <token>. It is shown once; copy it before closing |
| Revoke | Sets the device to revoked and tells gateways to remove its WireGuard peer. Cannot be undone; the device must enroll again |
Revoking from the list asks you to confirm Revoke Device. Selecting several rows and clicking Revoke revokes them in one pass and reports how many succeeded.
Device Policies tab#
The second tab, Device Policies, controls agent behaviour such as auto-connect and kill switch. See Device policies. Health checks and enforcement live under Security → Device Posture, reached from the Device Posture button; see Device posture.
Troubleshooting#
- A device shows “Tunnel down” while the user says they are connected. Heartbeats travel over HTTPS independently of the tunnel. The agent itself reported the tunnel down; check the agent log and the gateway it should reach.
- Posture says “Stale” although the device passed yesterday. Posture evidence expires after 10 minutes without a fresh check or heartbeat. Bring the device online so a new report arrives.
- “Policy evaluation is temporarily unavailable.” in the Posture tab. The posture overview call failed; click Retry evaluation. No enabled policy applies to this device. means the device is Not covered by any posture policy.
- “You don’t have permission to view devices.” Ask for
devices:view. “The device service is having trouble. Try again.” or “Couldn’t reach the device service. Check your connection and try again.” are transient; use Retry. - A restored device does not reconnect. Restore only clears the block. The agent still has to authenticate; revoked devices cannot be restored.