Reporting a Bug

If something looks wrong, behaves unexpectedly, or simply does not work the way you would expect, you can report it to the Trainery team without leaving the app. The report goes straight to our support inbox along with a snapshot of the page you were on and the browser you were using, so we can investigate without playing twenty questions.

Where to find it

Open the dashboard in any organization where you are signed in. Look at the very bottom of the left-hand sidebar — below your name and avatar you will see a small link Report a bug, sitting on the same line as the “Platform by Trainery” attribution.

The link is available to every authenticated user — members, trainers, admins, and owners — and behaves exactly the same regardless of your role.

If you are signed into the platform as a superadmin (separate app), the link is intentionally hidden — superadmins have direct access to the underlying logs and do not need the relay.

What to write

Clicking the link opens a small dialog with a single text field.

Write a short description of what went wrong, in your own words. There is no template — the more specific you can be the faster we can act on it, but anywhere from a sentence to a couple of paragraphs is fine. A few tips:

Say what you did. “I clicked Book on the Yoga 19:00 session” tells us more than “the button broke”.
Say what you expected to see. Even if it seems obvious, knowing your expectation helps us tell whether the bug is a regression or a UX surprise.
Say what happened instead. An error message, a blank screen, an unexpected redirect — anything observable.
Mention the time if it just happened. Server logs are easier to search when we know the approximate minute.

The description must be between 10 and 5000 characters. Submit when you are ready.

What is sent automatically

You do not need to repeat the technical details — the dialog captures them for you:

Current page URL including the active tab (?tab=…) where applicable.
Viewport size — the width and height of your browser window.
Browser and language — the user-agent string and your preferred language.
App version — the build identifier of the version you are running, so we can correlate the report with a specific release.
Your account — user id, email, role inside the current organization, and the organization slug. The server fills these in from your session — you cannot accidentally send a report from someone else’s account.
Time and IP — the server adds a UTC timestamp and your request IP for context.

We use these details only to investigate the report. Replies from the support team come back to the email on your account, so you can keep the conversation going if we need more information.

When you have a screenshot

The dialog cannot attach files. If the bug is visual or you have a screenshot that would be worth a thousand words, click the Email us instead link inside the dialog — it opens your default mail client with the subject and the current URL already filled in, and you can attach the image there.

The mailto address is support@trainery.app either way; the in-app dialog is just a faster path for text-only reports.

Demo tenant reports

If you are exploring Trainery on the public demo tenant, the Report a bug link works exactly the same — and your report still reaches the real support inbox. Reports from demo visitors are some of the most useful feedback we receive, so do not hesitate to use it. We mark demo-tenant reports clearly so the team can prioritize them and reply to you on your real email address.

Rate limit

To keep the inbox sane, you can submit at most 5 reports per minute from the same network. That is more than enough for the worst-case “I just discovered three bugs in a row” scenario; if you somehow trip the limit, just wait a minute and try again.

What happens next

A success toast appears once the report has been received, and the dialog closes automatically. There is no in-app status tracker — we deliberately keep the surface simple. If we need clarification or have a fix to share, we reach out by email.

If sending fails for any reason (network drop, server hiccup) you will see an error toast. Try again in a moment, or fall back to the mailto link.