# Account

> The Account page, where the station is connected to its Ganter account, its subscription and license seat are read, the integrator details are kept, and feedback is sent.

The **Account** page is the last entry of the rail's foot group and the only one drawn with
the brand mark instead of a glyph. It is about the station as a whole: the online Ganter
account the station is signed in to, the subscription that account holds, the license seat
this station occupies in it, who set the installation up, and the feedback form. Its title
reads **Account** and its description "Connect this station to your Ganter account, review the
subscription and its license seats, and send us feedback."

Two things are easy to confuse and are kept apart on purpose. **Local users** (the Users page)
are the people at this station, each with a role that decides what they may do on its
screens. The **Ganter account** (this page) is one sign-in that belongs to the station itself,
shared by every Windows user of the computer, and it decides nothing about screens: it is
what licenses the runtime. The two never gate each other, with one exception: connecting or
disconnecting the Ganter account, and editing the integrator details, takes a local
administrator (the Manage local users permission), because an anonymous operator must not
unbind the station's license.

The page opens for every identity. On the published demonstration it is off the rail: its
account and seat are fiction.

## The page {#the-page}

The page is a scrolling settings page with a left index of four rows in two groups:

| Group | Row | What it holds |
| --- | --- | --- |
| GANTER ACCOUNT | Account | The sign-in state: signed out, waiting for the browser, signed in (online or offline), with Sign in, Create an account and Sign out. See [Account](account-ganter-account). |
| GANTER ACCOUNT | Subscription | The plan and its status, renewal, the license seat gauge, the stations signed in to the account, the snapshot time, Manage subscription, and every license attention state. See [Subscription](account-subscription). |
| GANTER ACCOUNT | Developer & integrator | The support and maintenance contact, and the integrator ID with its looked-up public profile. See [Developer & integrator](account-integrator). |
| SUPPORT | Feedback | Report a bug, suggest an improvement or request a driver. See [Feedback](account-feedback). |

Opening the page refreshes the subscription snapshot and the integrator profile in the
background; the cards update when the answers land, and a failed refresh keeps what was cached.

## What the account is for {#what-the-account-is-for}

A station is **licensed** when it is signed in to an account whose subscription is active or
past due and the server has granted this station one of the subscription's seats. A licensed
station's runtime never stops. Anything else is **free mode**: every feature works, and the
runtime stops after a fixed window until someone restarts it at the station. The window is
one hour with nobody signed in and two hours signed in without a seat. The countdown sits in
the status bar and the whole conduct is described under
[Subscription](account-subscription#free-mode-and-the-runtime-countdown).

While the runtime is stopped this page is the one page that keeps rendering; every other
gives way to a paused notice. The status bar's message leads here ("Sign in for a longer free
window", "Add a license to remove the limit"), and the shell band above the rail carries the
**Restart runtime** button on the station's own window.

## What is sent where {#what-is-sent-where}

The account surface is additive and best-effort: nothing on the SCADA side waits for it, and
every network failure degrades to a cached state instead of an error. What leaves the station:

| When | What |
| --- | --- |
| Sign in | The browser flow with the Ganter server; the station stores only a refresh token, encrypted for this machine. |
| Sign in, boot, every 24 hours, and every time this page opens | The station registers itself with its random station id and the Windows machine name, plus the integrator ID when one is set, and fetches the subscription document. |
| Sign out | The station releases its seat and asks the server to revoke the refresh token. |
| Send (Feedback) | The report, with the app version and platform, under the account's token. |

Nothing else on the page leaves the station. The support and maintenance contact is stored
locally only. Crash reports are a separate flow with their own consent, on
[Crash reports](settings-crash-reports).

## The demo profile {#the-demo-profile}

The isolated demo profile (the seeded profile the documentation and smoke tooling run on)
does not talk to the Ganter server at all. Its Account page shows a local stand-in session:
the name **Demo profile**, the address `demo@ganterlab.invalid`, a Standard plan billed
annually, Active, one seat of one in use by this station. Signing out returns the profile to
free mode; Sign in restores the seat with no browser. Feedback cannot be sent from it.

## In this section {#in-this-section}

| Page | What it covers |
| --- | --- |
| [Account](account-ganter-account) | Sign in, Create an account, Sign out, the connected and offline states, the temporary identity notice, and what the sign-in belongs to. |
| [Subscription](account-subscription) | The plan and status texts, renewal, license seats, the stations list, the status time, Manage subscription, the attention states, and free mode with its countdown. |
| [Developer & integrator](account-integrator) | The support contact that never leaves the station and the integrator ID that does. |
| [Feedback](account-feedback) | The three report types, the fields, what is attached and sent, and when it cannot be sent. |