# Distributing builds to testers

Release Management offers a convenient, secure solution to distribute the builds of your mobile apps to testers without having to engage with either TestFlight or Google Play. Once you have installable artifacts, Bitrise can generate both private and public install links that testers or other stakeholders can use to install the app on real devices via over-the-air installation.

You can access all your distributable builds on the **Build distribution** page: these are the builds you can distribute to internal testers. Distributable builds are the following:

- For iOS apps, they are IPAs with Development, Ad-hoc, or Enterprise provisioning.
- For Android apps, only APKs are distributable to testers. AABs are not.

Each distributable build has its own page that includes installation instructions and metadata. The metadata includes, among other things, the source of the artifact, its creation time, size, and supported device types.

You can set up tester groups so that testers can get access to the build details page and install the app from there. Workspace owners, Workspace managers and project admins can also send notification emails to tester groups from the build page. For details, see [Tester groups](/release-management/build-distribution/tester-groups).

You can upload installable artifacts to the page from Bitrise CI builds or via our dedicated API. For details, see [Installable artifacts](/release-management/installable-artifacts).

## Accessing the build details page

To access the build details page on Bitrise:

:::note[Login required]

You need a Bitrise user account to access the build details page. The account must be a member of the project's team.

:::

1. Open your connected app in Release Management.
1. Select **Build distribution** on the left.
1. Select the **Builds** tab.
1. Find the build you need and click the arrow on the right.

   ![build-details-access.png](/img/_paligo/uuid-55dc2023-f61b-5331-f1af-94924727ff25.png)

## Installing artifacts

You can install build artifacts from its build details page. To do so:

1. [Access the build details page](#accessing-the-build-details-page) of the build.

   You can also access the build details page from a notification email.
1. In the **Install this version securely** card, install or download the build:

   - To open the page on a mobile device, scan the QR code with that device.
   - If your app is an Android app, click **Download artifact** to download the APK or AAB file.
   - If your app is an iOS app, open the page in Safari (not in a private window) on a device that is registered for your user and for this build, and click **Install**. If you can't install directly, use the **Download artifact** icon button at the top of the page to download the IPA file.
   - To share the page with another Bitrise user, click **Copy page URL**. Authentication is required to access this page.

## Enabling the public install page

The public install page allows you to distribute your installable artifacts to testers who don't have Bitrise accounts.

1. Access the build details page of the build.
1. Find the **Public install link** card and click **Manage access**.

   :::important[Required access]

   Only Workspace owners, project admins, and Release managers have the right to enable or disable the public install page for a build.

   :::
1. In the **Manage public install link** dialog, select **Enabled** and click **Save changes**.

   To turn the public install page off again, select **Disabled** and click **Save changes**.
1. Click **Get link** to open a dialog that contains both a URL and a QR code.

## Custom access link

You can quickly generate a shareable install link for an APK or non-store IPA artifact, with an optional expiration time and an optional access code. Those who receive the link can install the build without a Bitrise account.

:::note

This link is different from the [public install page](/bitrise-ci/deploying/ios-deployment/installing-an-ipa-file-from-the-public-install-page) link: the public install page is permanent and has no access controls.

:::

Users with the following [access roles](/release-management/configuring-connected-apps/release-management-roles-and-permissions) can create custom access links:

- Workspace owners
- Project admins

You can create multiple access links for the same artifact, with different expiration times, or no expiration time at all. All share links are publicly accessible to anyone who has the URL.

### Creating a custom access link

1. [Access the build details page of the build](/release-management/build-distribution/distributing-builds-to-testers).
1. Go to the **Public access** tab.
1. Click **New access link**.
1. Add a link name.
1. Optionally, check **Expiry** and set an expiry date for the link. After the provided date, the link will be no longer accessible.
1. Optionally, check **Access code** and set a code in the input field. Testers will need this code to access the link.
1. When ready, click **Create & copy URL**.

## Adding instructions for testers

You can set testing instructions for your testers for each installable artifact, let them know what's been added to a build and what you would like them to test.

You can check the instructions on the build details page of an installable artifact and on the [public install page](/bitrise-ci/deploying/ios-deployment/installing-an-ipa-file-from-the-public-install-page).

:::important[Editing access]

Users with the following roles can edit the testing instructions:

- Workspace owner
- Project admin
- Release Manager

Users with the App tester role have read-only access. For more information about roles, see: [Release Management roles and permissions](/release-management/configuring-connected-apps/release-management-roles-and-permissions).

:::

To add testing instructions to an installable artifact:

1. [Access the build details page](/release-management/build-distribution/distributing-builds-to-testers).

   You can also access the build details page from a notification email.
1. Find the **What to test** section, and click **Edit**.

   ![2025-09-04-rm-what-to-test.png](/img/_paligo/uuid-aac41e7c-0756-9d0b-d3a3-9fdf2db628dc.png)
1. Write a message to your testers, let them know what to test.

   The message has a limit of 4000 characters.
1. Click **Save changes**.
