In TestFlight, how does a public link enroll external testers, and what do its tester limit and criteria actually control?
answer
- created on an external group
- Open to Anyone or Filter by Criteria
- a limit between 1 and 10,000
- anyone can forward it
- testers show as Anonymous
basics
~20 sA public link is created on an external group and lets anyone holding it join; Filter by Criteria limits enrollment by device and OS, and Tester Limit caps how many can join through it, from 1 to 10,000.
solid answer
~50 sA **public link** belongs to an external group: under the group's testers tab you click **Create Public Link** and choose **Open to Anyone** or **Filter by Criteria**, which restricts enrollment by device and an OS range. **Tester Limit** caps how many people can join that group through the link, any number from 1 to 10,000. Anyone can forward the link, so people you never invited may join, and they appear as **Anonymous**: no name or email, though installs, sessions and crashes still show. Criteria apply at enrollment only, and testers can send feedback from any device. The group's insight cards warn when the link is full, a build is about to expire or no build matches the criteria, and the link's metrics count views, acceptances and testers who did not meet the criteria. You can change the criteria, the limit or disable the link at any time.
go deeper
Know that a public link invites external testers without collecting emails, and that it is created on an external group.
Explain the two modes, the 1 to 10,000 tester limit, the device and OS rules, and that criteria apply at enrollment.
Weigh the cost: forwarded links, anonymous testers you cannot contact, and insight cards warning of a full link or no compatible build.
Decide when a large anonymous panel is worth it and when a named, emailed group gives the team the follow-up it needs.
## What a public link is A **public link** is the second way to invite **external testers** in TestFlight, beside email invitations. Instead of naming each person, you create one URL for an external group and share it on social media, in messages, by email or anywhere else. Whoever opens it in the TestFlight app can accept and join that group, provided the group has builds available to test. Take a ski-resort app that wants a panel of season-pass holders: posting a link in the pass-holder newsletter is far easier than collecting hundreds of email addresses. The link brings two controls with it and one cost. ## Creating it 1. In the app's **TestFlight** tab, select a group under *External Testing*. 2. Under the testers tab, click **Create Public Link**. 3. Choose **Open to Anyone** (anyone can join) or **Filter by Criteria** (filter by device or platform). 4. Optionally click **Set Limit** under *Tester Limit* and enter a number between **1 and 10,000**. 5. For criteria, add at least one device with an OS rule, then confirm and copy the link. The OS rules are: | Rule | Who may enroll | |---|---| | From | testers on an OS version inside the range you give | | Newer than or equal to | that OS version or newer | | Older than or equal to | that OS version or older | | All supported (for platform) | any OS version for that platform | Later, **Manage** next to *Public Link* lets you add or edit criteria, set or change the limit, open the link to everyone, or disable it. ## What the controls do, and do not do - **Tester Limit** caps how many testers can join *this group through this link*. The app as a whole can invite up to 10,000 external testers, and every group draws on that. - **Criteria** decide **who can enroll** through the link. They do not follow the tester afterwards: the help pages state that testers can send feedback from any device they use, not only from devices that meet the criteria. - Builds in the group must be **compatible with the criteria**. If you filter for a recent OS and the only build supports something else, the insight cards flag that no compatible build exists. ## The cost: you lose who they are Anyone can share the link, so people you never invited may join. And a tester who joins through a public link is **Anonymous** in App Store Connect: - their name and email are not shown, although installation date, sessions and crashes are; - they are left out of the tester CSV export, whose names and emails would be anonymized anyway; - in feedback they stay anonymous unless they type an email address while submitting, and then it shows for that piece of feedback only. If you need to reply to specific people, invite them by email instead. An email invitation shows the tester's name, email address, installation date, sessions and crashes in the Testers section, and their email appears in each piece of feedback they send. Both methods can be used on the same group, so a team can keep a named core of testers and open the rest of the panel by link. ## Watching the link The group details page shows public link metrics over a 30-day period: - **Views in TestFlight**: how many testers viewed the link in the TestFlight app; - **Accepted**: how many accepted; - **Didn't Meet Criteria**: potential testers who failed the criteria; - **Didn't Accept**: those who declined, with the reason they chose, such as "It's not relevant to me". The insight cards at the top of the group also tell you when **the public link is full**, when there is **no compatible build**, or when **a build is about to expire**. You can deactivate the link at any time. ## Common mistakes - Treating the link as private: it is a bearer invitation, and anyone who has it can join until the limit is reached or you disable it. - Expecting criteria to keep an unsupported device from sending feedback. - Raising the tester limit and expecting it to lift the app's external ceiling of 10,000. Promoting the link, deciding which users to recruit and how the beta fits a release plan are matters for the team; TestFlight's part is the link, its limit, its criteria and what it hides.
- The season-pass panel needs replies from named testers; is a public link the right tool?Not on its own. Public-link testers appear as Anonymous, their names and emails are not shown and they are left out of the CSV export; their email shows only on a piece of feedback where they typed it. For people you must contact, invite them by email into a group, where their name and email are displayed.
- The group's insight card says the public link is full; what are your options?Click Manage next to Public Link and raise the tester limit, up to 10,000, or leave it full on purpose. Remember that all external testers of the app share a ceiling of 10,000, so raising one link's limit does not create room beyond that.
- Only people you sent the public link to can join the group.
- Public-link testers appear by name and email in App Store Connect.
- Tester criteria also block feedback from devices outside them.
- A link's tester limit raises the app's 10,000 external tester ceiling.
- A public link can only be disabled by deleting the group.