Skip to main contentGBOSSTABTime and Billing

Signing in on the desktop

Desktop appThe first-launch backend URL prompt and where the token is stored.

Signing in on the desktop

The desktop app talks to the same backend the web app does. How that connection is configured depends on which build your firm is running.

Production builds (the common case)

In the build your firm gives you, the backend URL is baked in at compile time. When you launch the app for the first time you go straight to the login screen, no URL field, no setup step. Sign in the same way you do on the web:

  • Demo mode: the page shows two Dev login buttons (Admin view / Accountant view). These exist for testing only and won't appear in a real production build.
  • Platform mode: click Sign in with GBOSS Platform. The app opens a browser window for IBM App ID, you sign in, and the desktop receives the session.

That's it. The session is valid for 7 days, the same as the web.

Generic / dev builds

If your build doesn't have a backend URL baked in, the login screen shows a Backend URL field at the top. You'll see it pre-filled with http://localhost:9080 (the dev default). Replace that with your firm's TAB URL, usually https://tab.<your-firm>.gbossone.com, and continue with the login buttons.

The URL you type is remembered between launches, so you only do this once per machine.

Changing the URL later

If your firm migrates to a new backend URL, open the in-app settings drawer:

  1. From the timer view, click the gear icon (top-right).
  2. Edit the Backend URL field.
  3. Click Save.

The next sign-in uses the new URL.

Where your session is stored

Per the desktop's design, the session token lives in a plain file at:

  • macOS: ~/Library/Application Support/gboss-tab/session_token
  • Windows (when the Windows build ships): %APPDATA%\gboss-tab\session_token

The file is created and read by the desktop app only, macOS file permissions keep it scoped to your user account. We moved off the OS Keychain in favour of this file storage because the keyring had a write-then-read inconsistency on some Macs (see Desktop troubleshooting if you ever run into login issues).

To sign out:

  • Click the gear icon → Sign out in the settings drawer, or
  • Right-click the system-tray icon → Quit (sign out happens on next launch when the session token expires)

Related