Build Distribution has always required testers to have a Bitrise account and project access. That’s fine for your own team, but it’s a real blocker when you need to get a build in front of QA contractors, stakeholders, non-technical product owners, or UAT participants who shouldn’t need to sign up for Bitrise at all.
Until now, the only workaround was manually flipping on the per-build “Public install page” toggle. No notifications, no group management, one build at a time.
External tester groups fix that.
What’s new
- Add testers by email, no Bitrise account needed. External tester group members are identified by email address only. They never need to create or log in to a Bitrise to install a build.
- Automatic email notifications. When a build goes out to an external group, members get an email with an access link to an install page. No manual sharing, no login required on the other end.
- Expiry dates and access codes. The access link can be further protected with an expiry date and an access code, so builds don’t stay reachable indefinitely.
How it works
- Create an external tester group for your app in Release Management/Build distribution, or add external members to an existing one by email.
- Create an access link to a test build and send out a notification via email to each group member.
- Each email includes an access link to the build’s install page with an optional expiry date and access code if you’ve set one. No Bitrise account is needed.