The Splashtop page at a glance
The one-field settings page that turns on Splashtop Business remote access: what the team owner email actually does, what the page looks like before and after you save it, and what that unlocks on the RMM device roster once a device reports in.
Remote Access, on Integrations > All
Splashtop is ezCyber's only Remote Access integration. Its card here reads Disconnected until a team owner email is saved. A tenant that has never touched this page at all reads Not Configured instead - same empty starting point, a different badge word for it.
The Splashtop settings page, before Save
The page header
Repeats the card's own name and one-line description, its connection badge, and the Remote Access category it belongs to. No permissions list and no API-scope card sit anywhere on this page - Splashtop has no API for this integration to call, so there is nothing here to request permission for.
Splashtop team owner email
The only field on this page: the email that owns your Splashtop Business team, not a device login. Typing it, and even saving it, never tests anything against Splashtop - Save just writes it down. Once saved, our agent reads each device's own Splashtop registry key and checks that key's domain against the domains you have already documented for your own company under Documentation > Domains. A domain match means ezCyber counts that device as managed by your team; no match still shows Splashtop as installed on the device, just not as yours. Nothing here is a password or an API key, and none is ever stored.
Saved: Configured, and what Sync health says
Configured, and Sync health
Save flips the badge to Configured and opens up Sync health, which is honest about doing nothing on a timer: "No scheduled syncs - this integration does its work on demand." The real payoff lives on a different screen: on RMM > Devices, a device your team manages shows a Splashtop mark in the Control column, but only once we have captured that device's Splashtop identifier from an agent poll - an identifier read from the device's own Splashtop registry key, never fetched over a Splashtop API. Click the mark and the session launches straight into the Splashtop Business app already installed on your own computer, already pointed at that exact machine: no console to open, nothing to pick from a list. Every click is still recorded - who started a session, and when. Northwind Demo carries no enrolled devices, so that mark itself is not pictured here; this page only shows what the settings screen itself does.
Why it works this way
The Control column mark is the same primitive on RMM > Devices and on a client's own Devices tab - there is no separate remote-control button on an individual device's own detail page.
A device only earns the Control mark once three things are all true: the Splashtop streamer is installed on it, our agent has polled it at least once since, and the domain on that device's own Splashtop account matches the team owner email saved here.
Other ways to do this
Why ezCyber doesn't build its own screen control
rmm/screen-control-what-we-recommend walks the positioning: what the Splashtop Business integration gives you today, and that ezCyber is still looking for a ScreenConnect partner to build the same one-click launch.
Every card on Integrations > All, in context
integrations/integrations-at-a-glance shows the whole Integrations > All page, Splashtop card included, alongside every other category.
Why ezCyber integrates instead of rebuilding
operational-guides/why-we-integrate-instead-of-rebuilding sets Splashtop alongside the rest of ezCyber's build-vs-integrate calls.
The rest of the roster this page's email lights up
rmm/the-devices-roster-at-a-glance walks RMM > Devices - Status, the machine, Health, client, Agent, last check-in and the row menu - the list the Control mark this page enables sits on the end of.
Was this helpful?