SynthIQ

Support Agent Identity

Per-host identity that the in-process SupportAgent uses to connect to SynthGateway. Backed by identity.json on disk via the shared /api/support_agent/identity controller (Synthology.Shared.SupportAgent 1.0.0.6). Phase 2E.1 / DCR-2026-205.

No restart needed. The in-process SupportAgent re-reads identity.json on every supervisor loop (DCR-2026-680, superseding the DCR-2026-054 startup-only read), so values saved below take effect within one heartbeat (about a minute) — no SynthIQ service restart required.

SynthGateway Identity

Stored in ….

Gateway URL (wss://…)

Tenant Slug

Agent Id String (e.g. synthiq@hospital-x)

Last written

—

SynthGateway Support Agent — Remote Support Consent (DCR-2026-679)

Controls whether Synthology support engineers may open an engineer-initiated remote support session to this system — your consent control, in addition to the license and your signed authorization (DOC-2026-329). Choosing Withdrawn blocks new sessions and ends any session already in progress within one heartbeat. Takes effect on the next heartbeat — no restart. Stored in .

Remote support consent

Last set

Remote Support Connector — provisioning status

The Synthology Support Connector is the dedicated cloudflared service that brokers engineer remote-support sessions. It needs a tunnel token supplied by Synthology at enrollment; until one is saved it stays installed but not provisioned and is deliberately not started. Provision it on Linux by putting an uncommented TUNNEL_TOKEN=… line (no export prefix) in /etc/synthology/connector.env, or on Windows by writing the token into C:\ProgramData\Synthology\connector\tunnel-token.txt. No restart is needed — the connector starts within one heartbeat. See Help → Remote Support Connector.

State

—

Provisioned

—

Provisioning source

—

Service installed

—

Licensed (remote_support)

—

Restarts

—

Last checked

—