Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Bucket members
  • Share individual builds

Was this helpful?

  1. Using Runway
  2. Build Distro

Sharing builds

PreviousBuild Distro bucketsNextInstalling builds

Last updated 7 months ago

Was this helpful?

Runway's Build Distro buckets make sharing builds straight forward. To grant access to a set of builds to members of your team, you have a few options:

  • Add individuals or user groups as bucket members: this grants users access to view and install all builds in the bucket.

  • Share individual builds with specific people: this grants users access to viewing and installing only the specific builds you share with them. This is a great option if you want to share a specific build without granting the user access to the entire bucket.

  • Enable org-wide access on a bucket: this will grant all users in your Runway organization access to viewing and installing all builds in the bucket.

There are two ways to share and distribute builds with your team in Runway: inviting team mates to be bucket members, or sharing specific builds with one or more of your team mates.

Bucket members

Add individual testers or user groups as bucket members to grant them access to viewing and installing all bucket builds. Bucket members can have one of three different roles:

  • Admin: Admin bucket members can edit bucket settings, manually upload builds to the bucket, share builds with individual testers, and install builds from the bucket

  • Uploader: Bucket members with the Uploader role can manually upload, view, and install bucket builds

  • Tester: Bucket members with the Tester role can view and install bucket builds. They can also update build tester notes.

You can add individual app users as bucket members or entire user groups which will grant bucket access to any app users with in the given user group.

Use the Share button in the build details drawer to copy a link to the build to your clipboard.

Share individual builds

If you don't want to share an entire bucket with someone, you can also choose to share specific builds with individual testers. Only bucket admins can share builds with individual testers. When you share a build with one or more testers, they'll appear in the "Shared with" section in the build details drawer. People that you've shared individual builds with will also get a Slack DM notification with the details of the shared build.

Builds that have been shared with you will appear in the “Shared with me” section.

If you share a build with an individual tester, they will be able to view and install that specific build, but they won't have access to other builds in the bucket.

🎛️