How many links can a build have?

Its own link plus up to 3 extra links on Pro, or up to 20 on Team.

Does the build's password apply on an extra link?

No. An extra link uses only its own password, or none. The build's pause, stop date and install limit do apply to every link.

Can I see which client installed?

Yes. Each link has its own install count, and the who installed list on the build names the link each install came through.

What does a client see after I turn their link off?

A page saying the link was turned off. Nothing changes for the other links or for apps already installed.

AppForShare Create a free account

One build, several links, each with its own password, end date and count

Pro (up to 3 extra links per build) and Team (up to 20)

An agency sends the same build to three clients. With one link, all three share one password and one end date, and when one engagement ends you cannot stop that client without stopping the others. Uploading the build three times works, but then you have three builds to keep apart.

Extra share links fix that. Each one is its own short link to the same build, with a label only you see, its own password, its own stop date, its own install cap and its own install count. Turn one off and the build and the other links keep working.

Start free See plans

Example

Shop app 2.5 (121), links

Client APassword, 12 installs
Client BStops Dec 31, 2026, 4 of 25 installs
Sales demoTurned off
Build total41 installs, all links included

Pro up to 3 extra links per build, Team up to 20.

Made for

Agencies that send one build to several clients
Teams that give QA, sales and a partner their own link to the same build
Anyone who wants to know which link the installs came through

What it ends

Three clients on one password, so changing it means telling all three
Uploading the same build twice just to get a second link
No way to end one client's access while the others keep testing
Not knowing which client installed a build

How it works

Step 1
Open the build
In the dashboard, open the build and find the Links card.
Step 2
Add a link
Give it a label such as Client A, and if you like a password, a stop date and an install cap. You get a new short link and QR code to the same build.
Step 3
Send it
Each client gets their own link. Testers never see the label; they see the build's install page as usual.
Step 4
Follow and change
Each link shows its own install count, and the who installed list names the link. Edit or turn off a link at any time.

What each link has

A link is its own short address, /i/ and a code, that opens this one build. Its label is for you only. If it has a password, that password is the one testers type on this link; the build's own password does not apply there. Its stop date and install cap count against this link's own installs.

A link opens only its build, not a list of other versions of the app. For a link that always opens the newest build, use a channel.

How it fits with the build's own controls

Installs through a link also count in the build's total. The build's pause, stop date and install limit apply to every link, so pausing the build stops all of them at once. Retiring the build does the same and sends testers to the newest build.

Turning a link off

A removed link stops at once: its page says the link was turned off. The build and its other links keep working, and the code is never given to another link or build.

From CI and AI tools

CLI 1.11.0: appforshare link add <build> --label "Client A" --password x --stop 2026-12-31 --max-installs 25, and link list, link edit and link rm. The CI API has GET and POST /api/ci/builds/:ref/links and PATCH and DELETE /api/ci/links/:link. The MCP server has list_build_links, add_build_link and remove_build_link; changes need your confirmation.

Good to know

Extra links point at one build. They do not follow new uploads; a channel link does that.
After a downgrade, links you made keep working. They can only be made stricter (a password, an earlier stop date, a lower cap) or removed.
Labels are for you. Testers see the build's install page, not the label.
Apps already installed keep working when a link is turned off.

Questions

How many links can a build have?: Its own link plus up to 3 extra links on Pro, or up to 20 on Team.
Does the build's password apply on an extra link?: No. An extra link uses only its own password, or none. The build's pause, stop date and install limit do apply to every link.
Can I see which client installed?: Yes. Each link has its own install count, and the who installed list on the build names the link each install came through.
What does a client see after I turn their link off?: A page saying the link was turned off. Nothing changes for the other links or for apps already installed.