Decide how long a link works and how many installs it gives
Pro and Team
An install link travels. A client forwards it to the whole office, a demo link from last month still gets opened, and a build with a crash keeps being installed while you fix it.
Link controls let you decide per build: pause the link now, let it run until a date, or stop it after a number of installs. Nothing changes on phones that already have the app.
Example
Shop app 2.5 (121), link controls
- LinkTaking installs
- Stop afterDec 15, 2026 (UTC)
- Install limit38 of 50
Made for
- Agencies that send a client a build for one review week
- Teams that demo at events and want a fixed number of installs
- Anyone who needs to pull a bad build without deleting it
What it ends
- Deleting a build just to stop new installs, then uploading it again
- Old links in client chats installing builds you no longer support
- No way to say "50 installs for the event, then stop"
How it works
Step 1
Open the build
In the dashboard, open the build and find Link controls under Settings.
Step 2
Pick a control
Pause the link, set a stop date (it stops after the end of that day, UTC), or an install limit. Leave a field empty to remove it.
Step 3
Testers see why
Instead of the install button they see a short message: paused, no longer taking installs, or limit reached, and ask you for a new link.
How installs are counted
On iPhone an install is counted when the phone asks for the app after the tester taps Install. On Android it is counted at the start of a download; a download that resumes after a dropped connection is not counted again. When the limit is reached, an install that already started can still finish.
From CI and AI tools
The CLI sets the same controls: appforshare link <build> --pause, --resume, --stop 2026-12-31 or --max-installs 50, with off to remove a date or limit. AI assistants connected through the MCP server can do it too, after you confirm.
Different rules for different people
These controls apply to the build and to every link of it. To give one client their own password, end date or install cap, add an extra share link to the same build: up to 3 per build on Pro and 20 on Team, each with its own count. Turning one off leaves the build and the other links working.
A build that should not be used any more
Pausing says the link is paused. When a build is broken and a newer one exists, retire it instead: its install page tells testers the developer retired it, shows your note and sends them to the newest build of the same app and platform, and channels skip it.
Good to know
- Controls affect new installs only. An app already on a phone keeps working, and AppForShare cannot remove it.
- Setting a control needs Pro or Team. After a downgrade, controls you set keep working and you can still remove them.
- For who may open a build at all, use a password (Free and up) or a private project with invited testers (Team).
Questions
- Does pausing delete anything?
- No. The build, its link and its install history stay. Turn the link back on and it works as before.
- What happens to a channel link if its build is paused?
- The channel still opens that build, and testers see the paused message. Put another build into the channel to change that, or retire the build: channels skip a retired build and open the one before it.
- Can two clients have different stop dates on the same build?
- Yes, with extra share links. Each link has its own label, password, stop date and install cap. The build's own pause, stop date and limit still apply to every link.
- Which plan do I need?
- Pro or Team.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- AppForShare Android store
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications