# Sign in and connect

> Linking a machine to your Triagic account or organization, what the License page reports, and working offline.

Source: https://triagic.com/docs/desktop/sign-in

## If your organization invited you [#if-your-organization-invited-you]

Sign in on the app's login screen with the **email and password your admin created
for you**. That is the same credential you would use on the web portal.

What happens on that first sign-in:

1. The app validates your credentials against the cloud, which is the only thing
   that can approve a login.
2. Your account is mirrored into the local database, so your session, history and
   attribution have a local identity to hang off.
3. The organization's configuration is pulled: playbooks, shared data sources, AI
   provider credentials, teams, the spend cap.

Give it a minute, then check **Integrations**. The shared data sources should be
listed. See [How configuration reaches the desktop](/docs/concepts/config-sync) if
they are not.

> **Note:** Being disabled takes effect immediately
>
> If an admin disables you in the portal, your next authenticated call fails. You do
> not stay signed in until the next sync.

## If you are using Triagic on your own [#if-you-are-using-triagic-on-your-own]

Sign in with your own Triagic account, the one you created when you signed up. There
is no account-less mode: every install is linked to an account, and signing in is
what links it. Your 14-day free trial starts from the day the account was created,
gives you one seat, and unlocks everything; you are your own admin until the org has
config to push down.

Signing in on a machine is also what **activates** it and what renews a machine
credential that has gone stale, so there is no separate activation step and no state
where a correct password is refused because this device's token aged out.

## Sign in with browser (passkeys) [#sign-in-with-browser-passkeys]

The login screen has a second button, **Sign in with browser**. It shows an eight
character code like `ABCD-2345` (the hyphen is just a separator) and opens
`triagic.com/device` in your browser. Sign
in there with a passkey (Touch ID, Windows Hello, a security key) or your password,
confirm the machine name, and press **Approve**. The desktop signs itself in within
a few seconds.

Why the browser and not the app: passkeys are bound to a web origin, and the desktop
window runs on a local address that has no such origin. The browser does the
cryptography; the desktop only ever sees the short code.

Register a passkey first under **Security** in the portal. Every account can have
them, owners and members alike. The password form stays; nothing about it changes.

The code expires after ten minutes. If the browser did not open, go to the address
the screen shows and type the code in.

## Plans, as the app reports them [#plans-as-the-app-reports-them]

The **License** page shows which plan this install is on, and links this machine to
your account.

| What it says                                           | What it means                                                                        |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------ |
| Trial                                                  | The 14-day free trial is running. One seat.                                          |
| Seat plan · *n* seats                                  | A paid license is active for *n* seats.                                              |
| Your 14-day trial has ended / Your license has expired | The account is expired. The app locks to this screen until you subscribe. See below. |
| Triagic couldn't reach the license server for too long | Offline past the 72-hour grace window. Reconnect and refresh.                        |
| Your system clock looks like it was changed            | Reset the clock and refresh to restore the license.                                  |

> **Warning:** Expired means locked, not degraded
>
> An expired account replaces the whole app with a license screen carrying a subscribe
> link. Nothing is deleted: your tickets, investigations, threads, playbooks and
> integrations are all still there and reappear the moment the subscription does.

Plan, seats, billing and the roster of activated devices are all managed in the web
portal's **Account** page, deliberately in one place, so two screens can never
disagree about how many seats you have.

## Working offline [#working-offline]

Once you are signed in, the app keeps working without connectivity: your session
stays valid, configuration stays as of the last successful sync, and licensing has a
72-hour offline grace window.

What does *not* work offline:

* **Signing in.** Credentials are checked against the cloud on every login. If the
  cloud cannot be reached the login is refused as unavailable, never as a wrong
  password, and never from a local cache. An already-open session is unaffected, so
  this only bites when you sign out or switch users while disconnected.
* **Investigations**, and anything else that needs your infrastructure or your LLM
  provider. Triagic being local does not make your production database local.

## Signing out and switching accounts [#signing-out-and-switching-accounts]

Signing out clears the session for this machine. Signing in as a different member of
the same organization re-mirrors that person's identity; the machine's link to the
organization is remembered separately from who is signed in.