Install and Offline Use

Fesk can be installed as a browser app. In a workspace you have opened before, you can keep working and create tickets when the network drops.

Installing Fesk

Use your browser's Install app or Add to Home Screen action while signed in. The installed app opens in its own window and uses the same account, workspace, and notification settings as the website.

What remains available offline

Previously loaded app assets, your last workspace, ticket form configuration, and recently viewed ticket data remain available from the local cache. Fesk shows an offline state when it cannot reach the server.

You can create a ticket while offline. Fesk saves it on this device, shows it as pending on the board, and creates it in the same workspace when a connection returns. Attachments are stored with the pending ticket and upload after the ticket has been created. If the ticket form configuration was not cached, you can still enter the basic ticket details; Fesk completes the ticket type selection during synchronization.

Keep the app or browser profile installed until pending tickets have synchronized. A ticket rejected by server-side validation remains on the device and is marked as needing attention instead of being silently discarded. Other changes may have more limited offline support.

Offline mode requires at least one successful signed-in visit on that device. A first launch after clearing browser site data still needs a connection so Fesk can verify the account and cache its workspace configuration.

Shared and public devices

Cached data and pending tickets belong to the browser profile. Signing out explicitly clears local offline data. On a shared device, sign out and remove the installed app or site data if the device should no longer retain workspace content.

For background alerts after installation, see Push Notifications.