# Feedback

> The Feedback row of the Account page, reporting a bug, suggesting an improvement or requesting a driver under the station's Ganter account, what is sent, and when it cannot be sent.

The **Feedback** row, under the SUPPORT group of the Account page's index, is a short form
that sends a report to Ganter. It has three kinds, one required line and one optional text,
and it sends under the station's Ganter account, which is why it lives on this page: a
signed-out station cannot send. It is not gated by any local role; anyone who opens the page
on a signed-in station can send.

## When it cannot be sent {#when-it-cannot-be-sent}

| Situation | What the card shows instead of the form |
| --- | --- |
| The station is not signed in to a Ganter account | "Sign in to your Ganter account above to report a bug, suggest an improvement or request a driver." |
| The isolated demo profile | "This session carries no Ganter account credential, so reports cannot be sent from here. Sign in again from the card above; a demo profile has no real account to send under." |

The form shows in both signed-in states, online and offline. Sending while offline tries to
renew the account's token first; when that fails the send is refused with "You must be
signed in to send a report."

## The form {#the-form}

| Field | What it is | Values / default | Effect |
| --- | --- | --- | --- |
| Type | The kind of report. | **Report a bug** (default), **Suggest an improvement**, **Request a driver**. | Changes the hint under Summary and the kind sent. |
| Summary | One line describing the report. | Up to 120 characters; required. | **Send** stays greyed until it holds something other than spaces. |
| Details (optional) | The longer description. | Several lines; no limit set on the field. | Sent trimmed; left out when empty. |

The hint under Summary follows the type:

| Type | Hint |
| --- | --- |
| Report a bug | Describe the problem and the steps to reproduce it. |
| Suggest an improvement | Describe the feature or improvement you would like. |
| Request a driver | Tell us which device driver you need. |

| Command | What it does | Greyed when (situation) | Not drawn when (role) |
| --- | --- | --- | --- |
| Send | Sends the report and reports the outcome in the action feed. | The Summary is empty, or the session cannot authenticate the call. | Never; the whole form is replaced by the notice above when the station cannot send. |

On success the feed reads "Thanks! Your "{Type}" was sent." and both text fields clear. On
failure the feed carries the reason and the text stays for another try:

| Reason | When |
| --- | --- |
| You must be signed in to send a report. | The account token could not be obtained or the server refused it. |
| The server refused this report because too many have been sent. Please try again later. | A sending limit on the server was reached. The answer does not say which one, and the limits are not published. |
| The server rejected the report ({code}). | Any other server answer. |
| The report could not be sent. | A failure with no further detail (a cancelled request, for instance); a network error shows its own message instead. |

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

| Item | Value |
| --- | --- |
| Kind | Bug, Suggestion or DriverRequest, from the Type. |
| Summary | The Summary, trimmed. |
| Detail | The Details, trimmed, or nothing. |
| App version | "Desktop {version}", the same version Settings > About shows. |
| Source | "Desktop/Windows". |
| Occurred at | The moment Send was pressed, in UTC. |
| Identity | The station's Ganter account token, so the report is attributed to that account. |

Nothing else is attached: no log excerpt, no screenshot, no configuration, no device list, no
local user name and no support contact. What you want Ganter to know goes in the text. A crash
is a different kind of report, captured automatically and sent only with your per-crash
consent from the dialog described under [Crash reports](settings-crash-reports); that one may
carry the crash details and may be sent anonymously. The Events console can produce a support
package, on the [Console](events-console) tab, if you need to hand over diagnostics alongside
a report.

## What the row does not do {#what-the-row-does-not-do}

- It does not queue a report for later. A send that fails is refused at once; the text stays
  in the fields until you send again or leave the page.
- It does not answer back. Replies, if any, reach the account's e-mail, not the app.
- It does not send while the station is signed out or on the demo profile.
- It does not attach diagnostics of any kind, and it does not send the runtime state.