Browser requirements

Tekst is a web application. There is nothing to install on your computer: you reach the platform by opening your organization's Tekst address (for example https://<yourcompany>.tekst.com) in a web browser. This article lists what that browser needs to support so the platform works correctly.

Supported browsers

Tekst supports the four major browsers:

Use the current stable version of one of these browsers, and keep automatic updates switched on. Older versions may still work, but they are not tested, and a browser that no longer receives updates from its vendor will eventually stop being able to connect (see "Secure connection" below).

Chromium-based browsers that are not in the table, such as Brave, Vivaldi, or Opera, generally behave like Chrome, but Tekst does not test against them. If you hit a problem in one of them, reproduce it in Chrome before reporting it.

What your browser needs to support

Secure connection (TLS 1.3)

Tekst is served over HTTPS only. No Tekst service accepts unencrypted traffic, and older protocols are deliberately switched off: SSL v2, SSL v3, TLS 1.0, and TLS 1.1 are disabled, as are weak cipher suites.

In practice this means your browser must support TLS 1.3. Every current version of Chrome, Firefox, Safari, and Edge does. A browser that is several years out of date, or a corporate proxy that only speaks older protocols, cannot establish a connection to Tekst at all and will show a generic connection or certificate error rather than the Tekst login page.

If you use an inspecting proxy or TLS interception appliance, make sure it supports TLS 1.3 and allows your Tekst domain through.

Cookies

Cookies must be enabled for your Tekst domain and for the sign-in page you are redirected to when you log in.

Tekst only uses functional cookies. They keep you signed in and hold your session state, and they are required for the platform to work. Tekst does not use tracking, analytics, or marketing cookies. Because these cookies are strictly necessary, there is no way to turn them off and still use the platform: with cookies blocked, you cannot log in.

Browser settings and extensions that block all cookies, or that clear cookies aggressively between page loads, will sign you out repeatedly. If a user reports being kicked back to the login page, cookie blocking is the first thing to check.

JavaScript

The Tekst interface is a JavaScript application that runs entirely in your browser. JavaScript must be enabled. Extensions that block scripts, such as strict content blockers or enterprise script policies, can leave the interface blank or partially loaded.

Network and firewall considerations

Your browser also needs a network path to Tekst:

• Your organization's network, proxy, or firewall must allow outbound HTTPS to your Tekst domain and to the sign-in domain used for authentication.
• If your organization uses single sign-on, the identity provider's domains must be reachable as well.
• If your Tekst project has the IP firewall enabled, you can only reach the platform from an approved IP address, regardless of which browser you use. See Set up the IP firewall.

For the IP addresses Tekst itself connects from when it reaches your systems, see Troubleshoot Firewall.

Mobile browsers

There is no dedicated Tekst mobile app. The web application is responsive and can be opened in a mobile browser on a phone or tablet. The same requirements apply there: a current browser, TLS 1.3, cookies, and JavaScript.

Mobile is suited to quick checks rather than day-to-day work. For heavier tasks such as building processes or configuring models, use a desktop browser where the full layout is available.

Browser extension

The Tekst Sidepanel is available as a browser extension, which has its own requirement: it is published in the Chrome Web Store, so you need Chrome or another Chromium-based browser that can install Chrome Web Store extensions. Firefox and Safari cannot install it.

• For Chrome, see Set up the Sidepanel as a browser extension.
• For Microsoft Edge, see Install the Sidepanel browser extension on Microsoft Edge.

If you work in the Outlook desktop application instead of a browser, see Set up the Sidepanel as an Outlook app.

Sessions

Your session is tied to the browser you signed in with. Sessions expire after a period of inactivity, after which you need to sign in again. The default is 24 hours and it can be configured for your organization. Logging out invalidates the session immediately.

Signing in from a private or incognito window works, but the session ends when you close the window, since the cookies are discarded.

Troubleshooting

If the problem persists after ruling these out, try a different supported browser or a private window with extensions disabled to confirm whether an extension is involved, then contact Tekst support at support@tekst.com with the browser name, version, and a description of what you see.

For the steps to sign in, see Log in to Tekst.