The client's RMM tab
What the RMM tab on a client record shows today: this client's own script and automation variables, an empty state with a door to create one, and where this client's per-device-type policy assignment actually lives instead.
What you will have
- Know what the client's RMM tab shows today: this client's own variable values, and nothing else.
- Read the empty state when no client-scoped variable has a value here yet, and use its door to create one.
- Give a client-scoped variable a value for this one client, and watch its status go from Not set to Set.
- Find this client's per-device-type policy assignment, since it is not on this tab.
Why it works this way
This tab used to list every RMM policy that applied to the client and let you override one of its fields right here. That is gone: a client that needs different policy values now gets its own named policy and an assignment instead, made on the client's own Devices tab or on RMM > Policies > Clients, never on this tab.
A client-scoped variable with no value set here fails any script or automation on this client that reads it. There is no fallback to a global value, so the Not set badge on this tab is a real warning, not decoration.
Steps
Open a client's record and click the RMM tab.
The tab now opens on two cards. Exclude from network mapping sits first: a single toggle reading "This client follows the fleet-wide network mapping switch unless excluded here," with a status line underneath naming that fleet switch's current state. Below it, with no client-scoped variable holding a value for this client yet, Variables shows its own empty-state message and a door to where variables are actually defined.
Open a client's record and click the RMM tab. Click Go to Variables, then New Variable, and set Scope to Client-specific.
A variable's scope is fixed once created: Global gives every client the same one value, Client-specific gives each client its own. This is the definition step the empty state's door points at - there is no way to create a client-scoped variable from the client record itself.
Click Go to Variables, then New Variable, and set Scope to Client-specific. Back on the client's RMM tab, the new variable already has a row here, marked Not set.
A client-scoped variable turns up on every client's RMM tab automatically the moment it exists. This one is just waiting on a value for this particular client.
Back on the client's RMM tab, the new variable already has a row here, marked Not set. Click the row, type a value for this client, and get ready to save.
Clicking a row swaps the card for a one-field form named after the variable's own key. A text or number value is trimmed before it saves; a secret variable's field is masked instead and never shows the stored value back.
Click the row, type a value for this client, and get ready to save. See the row read Set, with the value showing.
Saving returns to the list on its own. The badge and the value column are the only two places this client's own value for the variable is visible - the variable's definition page never shows any one client's value.
See the row read Set, with the value showing. For the policy this client's machines actually run, look at the Devices tab instead.
A "Policies for this client" strip sits above the device roster on the client's Devices tab: one policy picker per kind of machine, with a device count next to each and a link across to the same grid for every client. This is the second door onto the same assignment RMM > Policies > Clients edits - the RMM tab covered in the earlier steps never shows it.
For the policy this client's machines actually run, look at the Devices tab instead.
If it did not work
- If a value you saved here still is not what a script or automation sees, check the variable's own Allowed consumers list on RMM > Variables - a value can be saved and correct and still be invisible to the one consumer that was never checked.
- If you expected to see this client's policies on this tab, that view moved: check the client's own Devices tab for the per-device-type picker strip, or RMM > Policies > Clients for the same grid across every client.
Questions this page answers
What can I do on the client RMM tab?
It holds this client's own variables, the values your scripts and automations look up for this client. It no longer lists policies or lets you override a policy field here; a client that needs different policy values gets its own policy instead, assigned from RMM > Policies > Clients or from a tag on the client's devices.
What does "Exclude from network mapping" do?
Network mapping has one switch for the whole fleet (Settings > RMM > Network Mapping). When it is on, every client is mapped. This checkbox is the one exception. Turn it on for this client, and its devices stop being mapped. Everyone else stays mapped. Turn it off, and this client follows the switch again. If the fleet switch is off, this checkbox does nothing. No one is mapped either way.
Was this helpful?