Keep your SonicWall documentation in sync with reality.
SonicSaaS imports every SonicWall into IT Glue and syncs changes back automatically — so your documentation matches what the firewalls are actually running, without anyone copying it over by hand.
You onboard a client, document every SonicWall in IT Glue, and it's accurate — for about a week. Then firmware gets updated, an interface gets re-addressed, a rule changes during a 2am troubleshoot, and the documentation quietly stops matching the firewall. Nobody goes back to fix it, because keeping IT Glue current by hand across a hundred firewalls is a job no one has time for. We built SonicSaaS managing exactly that kind of fleet — and the documentation drifting stale was the part that bit us most.
Documentation that keeps itself honest.
Devices, imported automatically
Every SonicWall across every tenant shows up in IT Glue as a configuration — model, firmware, interfaces, all pulled from the device, not typed in by hand.
Changes that sync back
When a firewall's state changes, the documentation updates with it — so IT Glue stays current instead of going stale the moment you close the ticket.
A score for how accurate it is
The Documentation Health Score shows exactly where IT Glue matches device reality and where it has drifted — so you know what to trust.
From stale by Friday to always current.
Connect IT Glue once
Link your IT Glue account and map your organizations to the matching tenants. One connection covers your whole book of business.
Devices import and map
Every SonicWall imports as an IT Glue configuration with its real attributes — model, firmware, interfaces, configuration — read straight from the firewall.
Changes flow back, accuracy stays visible
As device state changes, the documentation updates and the Documentation Health Score shows how closely IT Glue still matches reality.
Documentation you can actually trust.
“Is my IT Glue actually accurate?”
The Documentation Health Score measures how closely each organization's IT Glue matches the live device state — so you know where to trust it and where to fix it.
“Do I have to type device details into IT Glue?”
No. Devices import automatically and their attributes come from the firewall itself — model, firmware, interfaces, configuration — so there's nothing to copy by hand.
“What about firewall passwords?”
Credentials are encrypted and held in SonicSaaS, never exposed to users or written into documentation — IT Glue gets the device record, not the secrets.
“Does this work across all my clients?”
Yes. Each tenant's firewalls map to the matching IT Glue organization, so documentation stays accurate across your whole book of business from one place.
Proving configuration compliance or auditing firmware too? Configuration compliance · Firmware audit
IT Glue sync, answered.
How do I sync SonicWall devices to IT Glue?
SonicSaaS connects to your IT Glue account and imports every SonicWall across your tenants as a configuration, then keeps it updated as device state changes — no manual data entry.
Does SonicSaaS keep IT Glue documentation up to date automatically?
Yes. It's a bidirectional sync: devices import into IT Glue and later changes flow back, so your documentation reflects what the firewalls are actually running instead of going stale after onboarding.
What is a Documentation Health Score?
It's a measure of how closely your IT Glue documentation matches the live device reality for each organization, so you can see exactly where the documentation is accurate and where it has drifted.
Are firewall credentials stored in IT Glue?
No. Device passwords are encrypted and held in SonicSaaS — never exposed to users — and IT Glue receives the device documentation, not the secrets.
Does the IT Glue sync work across multiple clients?
Yes. Each tenant's SonicWalls map to the corresponding IT Glue organization, so documentation stays accurate across every client you manage from a single login.
More for your SonicWall fleet.
Skip the slides.
Open the product.
Five minutes in the live demo and you'll know whether this belongs in your stack.