Beta Testing

Beta testing lets you run a private beta of your project. Invite a group of testers, tell them how to access a pre-release build, and collect their feedback separately from your public feedback board.

Enabling beta testing

1. Go to your project’s Settings page
2. Under Features, turn on Beta testing
3. A Beta section appears in the project sidebar

Beta testing is available on all plans.

Creating a beta program

A beta program represents one round or version you’re putting in front of testers.

1. Open the Beta section and click New beta program
2. Enter a name (and an optional version like 1.2.0)
3. Open the program to fill in the rest:
   • Summary — what you’d like testers to try
   • Access link — where testers get the build (TestFlight, a download, a staging URL)
   • Access instructions — any steps needed to get started
   • Status — Draft, Active, or Closed
   • Allow public sign-up — let anyone with the link join

Set the status to Active when you’re ready for testers to join and submit feedback. Closed hides the feedback form but keeps everything readable.

Inviting testers

There are two ways to enroll testers:

• By email — In the program’s Testers section, enter a tester’s email and send an invite. They receive a link that confirms their email and enrolls them in the beta.
• Public sign-up link — Turn on Allow public sign-up to get a shareable link. Anyone who opens it can enter their email and join after confirming it.

Testers are portal end-users, not team members — they never consume a paid seat. You can revoke a tester at any time; a revoked tester can no longer access the beta or submit feedback.

Reviewing feedback

Feedback appears in the program’s Feedback section, with the tester’s email, a category (bug, suggestion, praise, or question), and an optional severity. For each item you can:

• Change its status (open, triaged, resolved, won't fix)
• Reply to the tester

Beta feedback is private to the program — it never appears on your public feedback board or roadmap. New feedback also triggers your project’s notifications (email, Slack, and the beta_feedback.created webhook), following each member’s notification preferences.

Metering

Beta feedback submitted by testers counts toward your workspace’s monthly submission allowance, the same as feedback-board posts and private messages. Team members’ replies never count.