Skip to main content
This page covers rolling the desktop app out to your organization. For installing and using it, see Desktop App.

​
How users get the app

Users download installers from Settings → Desktop App. The page detects their operating system and offers a recommended build, with every platform listed underneath. Installers ship inside your TextQL deployment rather than from a public download site, so there is nothing to host and no external dependency to allow through a firewall. The page is only shown in a web browser — it hides itself inside the desktop app, since anyone seeing it there already has the app. That is the other common reason a user reports the download page missing. Because the installers travel with your deployment, the available app version is the one your deployment ships. A new desktop release reaches your users when your TextQL server is upgraded — not before. The same applies to automatic updates: the app checks your server for new versions, so cloud and on-prem deployments each offer exactly the version they ship.

​
Pointing the app at your server

If you run TextQL at a custom address, users would otherwise need to type that address on first launch. Instead, distribute a setup link:
Opening that link on a machine with the app installed points the app at your server. Send it in your onboarding email or push it through your MDM alongside the installer, and users go straight to signing in. The same URL scheme carries direct links to individual chats and dashboards — see Links that open in the app.

​
Hiding the download page

When organization branding is enabled, Settings → Desktop App is hidden. White-labeled deployments don’t advertise a TextQL-branded app, so the download page is suppressed to keep the deployment on-brand.
This is the usual reason a user reports that Settings → Desktop App is missing. If your organization uses branding but you still want people on the desktop app, distribute the installer and setup link yourself rather than pointing users at the page.

​
Network and routing

The desktop download path is served by compute and is excluded from the frontend authentication catch-all, with its own access-control rule. If you run with enforceAuth: true, this is what keeps the download and update endpoints reachable. Deployments installed from the official Helm chart already include this rule — no action needed unless you maintain custom Oathkeeper access rules, in which case preserve it. See Oathkeeper routing.

​
Supported platforms

There is no .rpm build. Windows 10+ is the only minimum the product states anywhere; macOS and Linux floors are set by the app’s Electron runtime and shift whenever it is upgraded, so they aren’t pinned here. Check Electron’s supported platforms for the current floor, or contact support@textql.com to confirm the matrix for a specific rollout.

​
Uninstalling

Uninstalling on Windows leaves the app’s local data in place, so reinstalling returns users to a signed-in app with their preferences intact. To reset a machine fully, remove the application data directory after uninstalling.

​
Need Help?

Contact support@textql.com.