Syncro Assets: machines, patches and RMM alerts

Switch on Syncro Assets and each company page counts its Syncro machines and patch rate, open Syncro RMM alerts reach your team as one alert per company instead of a stream, and the machines feed your dashboards and business reviews, all from the Syncro connection you already have.

Syncro is two products in one: a PSA and an RMM. Connecting Syncro brings the PSA half across. Syncro Assets is the second half, a read-only feed that lists each company's machines, what patches they are missing, what software is installed on them, and which RMM alerts are open right now. Its machines also count toward whitespace.

1. 1
   Add three permissions to the Current token's security group

   In Syncro: Admin, Syncro Administration, Security Groups. Tick Assets List/Search, Assets View Details and RMM Alerts List. Nothing else is needed, because nothing else is read.
2. 2
   Open Settings › Integrations and find Syncro Assets

   Press the Syncro Assets row in the RMM group to open its card. Only Tenant Admins can enable it.
3. 3
   Press Enable

   Current makes one cheap read to prove the permissions are really there, then writes the connection. A missing permission is named on the tile rather than showing up later as empty data.

One thing is deliberately left behind: an alert's raw output. That text is whatever the condition or script printed, which can carry a hostname, a file path, a user name or a fragment of the customer's own data, so Current mirrors the alert and not its output.

A machine is counted as non-compliant when it has failed patches, or when a missing patch is a security or critical one. It is counted as compliant when the patch read succeeded and neither of those is true. When the patch read has never succeeded for that machine, or the machine has no agent, compliance is unknown, and unknown is never counted as a failure. That is what stops a half-swept estate printing a compliance rate nobody measured.

Because the asset feed and the PSA share one account, a machine carries the same customer id Current already mirrored, so the match is exact rather than a name guess. Only if that fails does Current try the company name. When two or more of your companies share that name and the names differ only by a suffix like Inc or LLC, it links the one that is an active customer, or, if none of them is, the one linked to your PSA, and a name still tied is left unmapped rather than assigned to the wrong company. You can set a mapping by hand from the tile at any time, and doing so re-stamps the machines, the software and the alerts already stored.

Syncro's asset list is a mixed bag: agent-backed machines alongside hand-created records for printers, firewalls and spare laptops somebody typed in. Only agent-backed machines count towards endpoints, because a bigger endpoint count flatters every per-endpoint number and an automatic default must never move a number in its own favour. The hand-created records stay in the list, where they are useful for sizing an account.

Open Syncro alerts feed the same two rules your other RMMs feed, so nobody gets two alerts about one noisy estate. Syncro does not publish a severity, so a Syncro alert counts towards the warning level and can never reach the critical one: a workspace on Syncro raises the warning at three alerts open at once. Alert titles carry counts, never a machine name.

The machine list is cheap and fills quickly. Patches and software are one call per machine, against the same 180-calls-a-minute budget every Syncro workspace shares, so Current works stalest-first and refreshes a machine's patches about weekly and its software about monthly. A person pressing Sync now on any Syncro surface always outranks this feed. A run that hits the budget stops cleanly, keeps its place, and says so rather than showing a failure.

• Syncro is disconnected: the tile says the asset feed uses that connection and asks you to reconnect Syncro first.
• The token is gone: run Test connection on the Syncro card.
• Syncro refused the token: the tile says the token failed, which usually means it expired.
• A permission is missing: the tile names the exact checkbox, Assets List/Search.
• In every one of those cases the machines, software and alerts already read stay on screen with their age shown. Nothing is deleted because a call failed.

Admins and sales leadership see everything; everyone else sees the machines belonging to a company they can already view. Partner (read-only) viewers never see any of it, and that is blocked at the database rather than hidden in the interface.

Disconnect on the Syncro Assets tile stops the feed and leaves the Syncro PSA connection alone. Everything already read stays where it is and simply stops updating, and enabling it again picks up from there with your mappings intact.