Give one client its own script values on its RMM tab
Give each client its own values for the variables your scripts and automations read, such as a per-client onboarding key kept encrypted, so one script serves every client, and exclude a single client from network mapping.
See it
Browse
On this page
How to do it
Open a client's record and click the RMM tab.
The tab has two cards. Exclude from network mapping is a toggle: this client follows the fleet-wide network mapping switch unless excluded here, with a status line naming that switch's current state. Variables lists this client's own values. Until a client-specific variable exists, it says No client variables defined yet and offers Go to Variables.
Define the variable once under RMM > Variables.
Pick Variables on the left side bar, then click New Variable. Key is the name scripts reference: letters, digits and underscores, starting with a letter, and it cannot change later. Give it a Label such as Onboarding Key and a Type of Text, Number, Yes/No or Secret. Set Scope to Client-specific. Under Allowed consumers tick which of Scripts, Automations, Email and Assistant may read it. Secrets default to Scripts only.
Back on the client's RMM tab, the new variable has a row marked Not set.
A client-specific variable shows up on every client's RMM tab as soon as it exists. This client's row waits for a value.
Click the row and type this client's value.
The form is named Set value with the variable's key. A Text or Number value is trimmed before it saves. A Secret field is masked, stored encrypted and never shown again, and a blank value is refused.
Save, and the row reads Set.
Saving returns to the list. The status badge and, for non-secret values, the value column show this client's own value. With delete access, the trash icon clears the value, and a script run that reads it fails for this client until a new one is set.
Save, and the row reads Set. Exclude a client from network mapping when it needs to opt out.
Network mapping has one fleet-wide switch under Settings > RMM > Network Mapping. When it is on, every client is mapped. Turn on Exclude from network mapping for this client and its devices stop being mapped while everyone else stays mapped. If the fleet switch is off, the exclusion is saved and takes effect when the fleet switch is on.
Set this client's policy on its Devices tab.
The Policies for this client pickers, one per Workstation, Server, Mac and Linux, are in the Agent setup drawer on the client's Devices tab, and RMM > Policies > Clients edits the same assignment for every client. To change it from chat, ask Elise: "Put Bluebird Dental's workstations on the Healthcare policy." She shows the before and after for one-tap approval.
What you will have
- Define a client-specific variable once and give each client its own value on its RMM tab.
- Keep a secret such as an onboarding key encrypted and never shown again.
- Watch a variable go from Not set to Set.
- Exclude one client from network mapping while everyone else stays mapped.
- Find where this client's policy for each kind of machine is set.
Why it works this way: Give one client its own script values on its RMM tab
One signed script serves every client. The script names a variable, and each client's tab holds that client's own value, so you keep one script and N values instead of N copies of the script.
A client-specific variable with no value fails the script run for that client. There is no fallback to a global value, so the Not set badge is a real warning, not decoration.
A value reaches a script as data and is never pasted into the script's text. A Secret is stored encrypted and never shown again after saving.
The platform also fills in built-in values for each device, client and MSP on its own, so a script can read a device or client name without you defining a variable.
If it did not work: Give one client its own script values on its RMM tab
- If a value you saved is still not what a script or automation sees, check the variable's Allowed consumers on RMM > Variables. A value can be correct and still be hidden from a consumer that was never ticked.
- If you expected this client's policies on this tab, they live on the client's Devices tab and on RMM > Policies > Clients.
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?