Understanding The Devices List

The Devices page (left nav → Devices) is the central inventory of every endpoint across all your customers. This guide covers its columns, search, filters, views, and the per-device actions menu.

Layout

The page header has Devices, a view toggle (table / card-grid), and Add Device. Below that sit a Search for Devices box and a Device Tags filter button. A device count (e.g. 289 devices) sits at the top right of the table.

Columns

Device — device icon and hostname.
Status — a colored badge (ONLINE / OFFLINE / PENDING / ARCHIVED) with the last check-in timestamp underneath.
OS — operating system with icon (Windows, macOS, etc.).
Customer — the organization the device belongs to (e.g. Default, test 1).

Each row ends with a … actions menu and an open arrow that jumps to the device's detail page.

Searching

Type in Search for Devices to filter the list by hostname in real time.

Filtering

Column headers with a funnel icon are filterable:

Status filter — click the funnel on Status to pick any combination of Offline, Pending, Online, or Archived. Use Select All, then Apply to filter or Reset to clear.
OS and Customer columns filter the same way, so you can narrow to a platform or a specific organization.

Device Tags filter

Click Device Tags to open the Sort and Filter dialog. Tick one or more tag keys (e.g. test_tag, new_tag) and hit Apply Filters, or Reset Filters to clear. This is how you slice the fleet by your own tagging scheme.

Views

The view toggle (top right) switches between:

Table view — the default row-based list with full columns.
Card/grid view — a tile layout of the same devices.

Pick whichever is easier to scan; both reflect the same filters and search.

Clicking … on a row opens an actions menu. Available actions include:

Remote Shell — open a command-line session (has a submenu for shell options).
Remote Control — start a remote desktop session (opens in a new window).
Manage Files — open the file manager for the device.
Run Script — run a saved script on the device.
Archive Device — move the device to archived status.
Delete Device — permanently remove the device (destructive).

Remote actions need the device to be online with a healthy agent — otherwise they're greyed out.

Adding a device

Use Add Device (top right) to enroll a new endpoint. New or unassigned devices show up under the Default customer until you reassign them.

Tips

Stack search + Status + Customer filters to isolate something fast — e.g. all the offline Windows devices for one client.
The same Devices list (same controls and all) shows up inside each customer's Devices tab, pre-scoped to that organization.
Use the Status timestamp to judge how fresh the data is — an old "last seen" on an OFFLINE device means it dropped off a while ago.

Frequently Asked Questions

MSP AI Agents

Can AI Agents Really Close Tickets Without a Technician?

Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.

How Much Can AI Agents Save an MSP?

On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.

AI MSP

Which Tasks Should an MSP Automate First?

Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.

IT Documentation

What Is Hudu Used For?

Hudu is IT documentation software that MSPs and internal IT teams use to centralize client documentation, network details, encrypted passwords, IT assets, and SOP runbooks in one searchable platform, so technicians find what they need without digging through scattered files.

EDR Security

Is SentinelOne Good for MSPs?

SentinelOne is a strong fit for MSPs that want autonomous detection, one-click ransomware rollback, and real multi-tenancy across Windows, macOS, and Linux. The trade-offs are a dense console, premium pricing, and a tuning period that produces false positives early on.

Endpoint Security

Is CrowdStrike Falcon Good for MSPs?

Yes, for security-led MSPs and MSSPs serving mid-market or compliance-driven clients. The detection and threat hunting rank at the top of the market, and Flight Control handles multi-tenant management. It fits poorly for books made up of many small clients on tight budgets.

What Does Bitdefender GravityZone Do?

Bitdefender GravityZone is a cloud-native endpoint protection platform that combines prevention, EDR, and XDR in one agent and console. For MSPs, it adds multi-tenant management, so one team can protect and monitor every client's endpoints from a single dashboard.

Is Sophos Intercept X Good for MSPs?

Yes, for MSPs that want one vendor across endpoint, firewall, and managed detection. Sophos Central Partner gives true multi-tenant control, and MSP Connect Flex bills monthly by usage. Plan around occasional CPU spikes on busy servers and a console learning curve.

Sophos XDR

What Is Sophos XDR?

Sophos XDR is extended detection and response built on Intercept X. It correlates telemetry from endpoints, the Sophos firewall, email, cloud, and identity inside Sophos Central, then lets technicians hunt across that data with Live Discover queries.

Microsoft Defender XDR

What Is Microsoft Defender XDR?

Microsoft Defender XDR is Microsoft's extended detection and response suite. It unifies endpoint, email, identity, and cloud-app threat signals into one Defender portal, correlating related alerts into single incidents so teams investigate one timeline instead of chasing scattered, disconnected alerts.