Handle users' feedback and forward it to the vendor

What it is for

Users report bugs and suggestions directly in BrowserDesk (F9). The reports go to your relay — not automatically to the vendor. In the console you work through them: set the status, forward to the vendor at the push of a button or, with a GitHub repository of your own, create an issue.

What you need

• Your own relay from version 20261010.26.
• A console account as system administrator of the relay.
• For GitHub issues: a GitHub repository and a GitHub token for it.

How to do it

1. In the console open Support › Feedback. The top right shows how many are still open.
2. Filter at the top: Open, Done, Rejected or All.
3. Each report shows title, number, kind (Error or Suggestion), time, the stated device ID and the text. Diagnostics expands version, platform and — if the user attached it — a log excerpt.
4. Set the status: in the selection on the right, New, In progress, Done or Rejected.
5. Forward to the vendor: Forward to the vendor → confirm. The report then says "Forwarded to the vendor" with the time.
6. Create a GitHub issue (optional): first, at the top right, Settings → GitHub repository (owner/name) and the token → Save. Then every report shows Create GitHub issue.

How you know it worked

• After changing the status the console reports "Status saved."
• After forwarding: "Forwarded to the vendor."
• After creating: "GitHub issue created." — the report shows the button GitHub issue leading to the issue, and the status changes to In progress.

What the other side sees

After sending, the user sees "Rückmeldung gesendet" (feedback sent). The status you set does not get back to them today.

Good to know

• Nothing leaves your premises on its own. Only what you forward is forwarded. The device ID and IP address are not passed on — neither to the vendor nor to GitHub.
• Statements, not proof: the sender states the device ID and platform themselves. If you need to rely on them, check them in the device list.
• Against flooding: at most 5 reports per hour and sender address, 300 per day in total.
• Data protection: a report contains personal data (text, device ID, address, optionally a log excerpt with computer names). The legal texts mention this; on your own relay you are responsible for it.
• The GitHub token is stored encrypted only on your relay and is never shown again.
• The vendor address is preset to https://browserdesk.de and can be changed under Settings → Vendor address for “Forward”.
• Cloud: reports from devices in the Cloud go to browserdesk.de, where the vendor handles them. Cloud customers cannot use this view.
• The console's empty-list text tells users to use "Settings → Send feedback"; in the German program the button is called Rückmeldung senden (send feedback).

If it does not work