Research mass deployment support for draw.io Desktop

[davidjgraph]

We want a clear picture of how large organisations deploy draw.io Desktop across managed fleets, what we already support, where the gaps are, and concrete next steps (docs and/or features).
Background

draw.io Desktop is an Electron app that gets pulled into enterprise environments because it runs fully offline with no account. IT teams deploy via MDM and want silent installs, locked-down config, and controlled updates. Our guidance for these admins is currently thin.
Scope (research areas)

• Silent / unattended install per platform: Windows installer flags and whether an MSI is offered, macOS pkg for MDM, Linux deb/rpm/AppImage/snap/flatpak
• Per-machine vs per-user install behaviour
• Centralised config: how to pre-set and lock defaults (save location, disabling cloud storage targets, plugin allow/deny). Document config file paths, env vars, registry keys, plist
• Update control: disabling or pinning auto-update in managed environments, offline update flow
• Offline / air-gapped operation: confirm no required outbound calls, document any telemetry and how to switch it off
• Deployment tooling: test and document Intune, SCCM, Jamf, Group Policy. Note what exists vs what's missing
• Security review pack for IT reviewers: code signing / notarization status, what data is stored and where, Electron hardening (context isolation etc.) we can point them to

Deliverables

• Short writeup of current capabilities vs gaps
• Draft admin deployment guide, or a list of doc additions needed
• Feature requests filed for any missing config or locking capability
• Verified install on at least one MDM platform

[ManishPrakkash]

I would love to work on this issue if it is still available.

[davidjgraph]

Unfortunately, we don't accept code from outside the code team.

[ManishPrakkash]

my bad... anyways thank you if any issues to address feel free to address anytime