Feedback Forms

Feedback Forms are branded, BetaHub-hosted pages that collect feedback from anyone you share a link with. Each form has its own link you can drop into a Discord channel, a newsletter, or your game’s website — no widget to embed and no plugin to ship. A submission lands in your project exactly like any other: a bug form opens an Bugs report, a suggestion form opens a Suggestions, and a ticket form opens a Tickets entry.

How It Works

1. Create a form — Pick what it collects: bugs, suggestions, or tickets.
2. Customize it — Set who can submit, add your branding, and attach custom questions, all against a live preview.
3. Turn it on and share — Enable submissions, then copy the form’s link and post it wherever your players are.
4. Read the results — Submissions arrive in your project’s normal Bugs, Suggestions, or Tickets lists.

Where to Find It

Feedback forms live in the Forms & Surveys area of your project’s sidebar, alongside Surveys and hubs. Managing forms is available to Developers and project admins.

Creating a Form

From Forms & Surveys, choose New bug form, New suggestion form, or New ticket form. The builder opens with your settings on the left and a Live preview on the right that updates as you type — nothing is saved until you choose Create form (or Save changes on an existing form).

Form Settings

**Who can submit** controls who can use the form:

• Anonymous allowed — anyone with the link can submit, no account needed.
• Sign in required — anyone with the link can submit, but must sign in first, so every submission is attributed to an account.
• Disabled — the link is turned off.

Contact decides whether you can follow up with the person who submitted:

• Optional — allow anonymous — the submitter may leave a way to reach them, or stay anonymous.
• Required — ask for an email — the form asks for an email (or a Discord connection) before it will submit.

On the public page, the contact step offers a plain email field — and, when your project has Discord connected, a Connect with Discord button — so players can choose whichever they prefer.

The rest of the settings shape the page itself:

• Title and Include a title field — set the heading players see, and optionally let them give their own report a short title.
• Intro text — a sentence or two shown above the form.
• Attachments — every form can accept optional uploads: screenshots, video, logs, or any file.
• Custom questions — attach any of your project’s player-settable custom fields (for example a Platform dropdown) to collect structured, project-specific answers.

Branding

Every form can match your game’s look. In the builder you can set:

• Accent color — the color of buttons and links on the public page.
• Theme — Visitor choice (the visitor’s own light/dark preference), or force Light or Dark.
• Logo — shown at the top of the page.

Sharing a Form

A brand-new form starts with its link off. Set Who can submit to Anonymous allowed or Sign in required and save — the Copy link and Open buttons then appear. Use Copy link to grab the URL, or Open to preview the live page. The form keeps accepting submissions until you switch Who can submit to Disabled again.

Hubs

A hub groups several forms — and Surveys — under one branded link, so you can share a single “give us feedback” URL instead of many. A hub can present its members two ways:

• Chooser — a landing page that asks “what would you like to do?” and lets the visitor pick a form.
• Switcher — tabs across the top, so the visitor can move between forms on one page.

Each form or survey in a hub still keeps its own standalone link, so adding something to a hub never breaks a link you’ve already shared.

See Also

• Surveys – Ask testers structured questions and read the results
• Public Suggestions Board – A public, votable board of suggestions
• Public Bug Board – Share known issues publicly
• Custom Fields – Collect structured, project-specific data