The client's Devices tab
The install doors, the policy assignment and the device roster for one client, all on its own record - the same components the fleet-wide RMM pages render, scoped down to just this client.
What you will have
- Know what the client's Devices tab shows: the same install doors, policy assignment and device roster as the fleet-wide RMM pages, scoped to this one client.
- Generate this client's own install key, and see where its downloads and Regenerate button live.
- Find the one-time, single-use install link, and know when to reach for it instead of the install key.
- See which policy each kind of machine on this client gets, and where to change it for every client at once.
- Read the roster's empty state honestly, and know what changes once a device enrolls.
Why it works this way
This tab is not a separate device system: the Install Keys card, the policy chips and the device roster underneath them are the exact same components the RMM > Devices pages render, scoped to this one client - a key generated or a policy set here is the identical record the fleet-wide grid would show.
The title-line "Install agent" button the fleet-wide RMM > Devices page shows next to its own heading does not appear on this tab. The Install Keys card's own "Generate default install key" button, right under the section header, is this tab's install door instead.
Steps
Open a client's record and click the Devices tab.
The tab opens on "Agent Installer & Management": manage the client's install keys, review enrolled agents, and, when you need it, mint a one-time link. On a fresh client the Install Keys card is empty, with a single "Generate default install key" button and nothing else on the row yet.
Open a client's record and click the Devices tab. Click Generate default install key to mint this client's key.
The card now shows the default key on its own row, with a copy button and Regenerate - the default key can only be regenerated, never revoked, so it keeps working no matter what. Underneath sit the EXE, MSI and Linux installer rows, each collapsed behind a caret with a Download button always visible at the right, and a Quick troubleshooting tips panel. Add named key, at the bottom, mints a second key that can be revoked - the one to use when a push might leak the credential.
Click Generate default install key to mint this client's key. Open "One-time install link (advanced)" for a single-use link instead.
This is a different credential from the install key above: Generate agent installer mints a link that self-expires in 24 hours and works exactly once. Most deployments use the install key from step 2 instead; reach for this only for a single, one-off field install.
Open "One-time install link (advanced)" for a single-use link instead. Look at Policies for this client, the chip row above the roster.
One picker per kind of machine - Workstation, Server, Mac, Linux - each showing the policy this client's devices of that type actually run and how many devices are on it. A blank picker means the client gets the default policy set for every client. Every client, at the top right, opens the same grid across every client at once (RMM > Policies > Clients) - the same assignment, a different frame around it.
Look at Policies for this client, the chip row above the roster. Look at the device roster underneath: no devices yet.
Roster and Unapproved are the same two tabs the fleet-wide RMM > Devices page carries, just narrowed to this client - there is no Client column here, since a column of one repeated name would be noise. On a fresh client the roster reads "No devices yet. Add one to get started." with full column headers (Device, Health, Agent, Security, Control, Last check-in) and zero rows. Tool coverage, folded below the roster, is the one card on this tab that depends on a connected RMM or EDR integration rather than this client's own agent data.
Look at the device roster underneath: no devices yet.
Other ways to do this
From RMM > Devices, filtered to one client
Open RMM, then Devices, and set the Client filter to this client.
If it did not work
- No "Generate default install key" or "Generate agent installer" button, only quiet cards: the account viewing this tab does not carry this client's edit tier.
- No Devices tab at all in the client's own tab strip: this tab only shows on an MSP-module instance.
- Expecting a title-line "Install agent" button like the fleet-wide RMM > Devices page: this tab does not have one. Use the Install Keys card below the section header instead.
Was this helpful?