Administration
Yavaren support and your on-prem installation
What Yavaren support can see of an on-prem installation, what it can do and only when you allow it, how to approve or end a support session, and the kill switch.
Yavaren support never connects to your installation. Your installation calls out to Yavaren (the Cloud Link) and asks whether support has requested anything. Your administrators decide what is allowed on Platform admin › System › Support access.
What Yavaren can see
While your installation is linked, Yavaren support sees its health: the version, the licence, whether the database, document store, audit chain and runners are healthy, how long work waits, the readiness checks, when the certificate ends, and where your configuration differs from what Yavaren recommends. A secret is never shown, only whether it is set. In restricted mode Yavaren sees only versions, the licence, whether each part is healthy and how many readiness checks pass.
What Yavaren can do, and when
Only a short list of actions, each signed by Yavaren and checked by your installation before it runs: collect a diagnostics bundle, fetch recent log lines of every part of the control plane and, if asked, of your runners (credentials removed; never a job's log), run the readiness checks or a connection test, change one of a list of operating settings, restart the link or the control plane gently, restart runners (one, a pool or all, a few at a time so work goes on; a job in hand finishes or is handed back and retried), upgrade to a published release (rolled back on its own if the new version is not healthy), rotate the link's token, and turn maintenance mode on or off. Never a command, code or a file to run. Your runners are never reached from outside: they pick up a restart from their own next call to your control plane.
| Your choice | What happens |
|---|---|
| Support sessions (the default) | Yavaren asks for a session: which actions, for how long, and why. An administrator approves (maybe shorter, or fewer actions), or denies it. You can open one yourself during a support call, and revoke any session at once |
| Full remote management | Offered only if your contract with Yavaren includes it, and only after one of your administrators allows it here. Yavaren can then run the listed actions without asking each time. Withdraw it at any time: from that moment every action needs a session again |
| Kill switch | Stops everything at once: nothing runs, every session ends, and your installation stops asking Yavaren for work. An upgrade Yavaren started stops too, and if it had already switched versions, your previous version is put back. Health is still sent while you stay linked |
Everything Yavaren asked for, who asked, why, whether it ran and its result is listed on the same page and in your audit log. Your own administrators can restart runners themselves on Platform admin › Fleet › Runners, and read the recent log lines of every part of the installation on System › Logs.
Without a link
An air-gapped installation sends and receives nothing. Yavaren support can give your administrator a signed file (diagnostics only); importing it on Support access runs it and gives you a result file to send back. You can also download a support bundle from System › Support bundle and send it yourself.