> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/using-runway/app-settings/release-pilot-rotation.md).

# Release pilot rotation

Configure the release pilot rotation for your app.

### About release pilots

Generally speaking, **Release pilots** are the team members given the ultimate responsibility of overseeing each release and resolving blocking issues that may arise. By default, release pilots have broad permissions to perform actions within releases in Runway, will be specifically pinged by certain notifications, and will be responsible for completing checklist items assigned to the Release pilot role.

### Managing your release pilot rotation

The release pilot rotation is a list of app users that Runway loops through to automatically assign release pilots to upcoming releases in Runway. 

In the **Release pilot rotation** page in App settings, you can add, remove, replace, or swap users in the release pilot rotation, as well as manually update the order of the list. 

<figure><img src="https://727226624-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MjFmyReUsbJqDjHEAlW%2Fuploads%2FLegfHLWVfDcAjIR3BNud%2Fimage.png?alt=media&amp;token=2201fe8c-6dc9-48d4-b260-b8c73f415b74" alt=""><figcaption></figcaption></figure>

Upcoming releases and their predicted release pilots are shown on the release pilot rotation view. Two cycles of the rotation are previewed in the list.

{% hint style="success" %}
Runway does not assign the next release pilot in the rotation for hotfix releases. Instead, the hotfix release inherits the release pilot from the "parent" release.&#x20;
{% endhint %}

{% hint style="warning" %}
For a user to be eligible to be added to the release pilot rotation, they must be part of a [user group](/using-runway/organization-settings/team.md#groups) with the **Eligible for release pilot rotation** option enabled via [Organization settings](/using-runway/organization-settings.md).
{% endhint %}

{% hint style="warning" %}
Release pilots have their full permissions at all times, whether or not they're currently assigned in the rotation.
{% endhint %}

{% hint style="info" %}
A release pilot can always be changed for a particular release, either by clicking **Edit release settings** on the Kickoff step, or straight from the release pilot rotation list in App settings (see [Changing the pilot for a single release](/using-runway/app-settings/release-pilot-rotation.md#changing-the-pilot-for-a-single-release)). Either way, the change displays as an **override** in the rotation view and doesn't affect the rest of the rotation.
{% endhint %}

{% hint style="info" %}
To disable automatic assignment of release pilots from the rotation, simply remove all users from the release pilot rotation. Note that you'll need to manually choose a pilot for each release.
{% endhint %}

### Release pilot rotation settings

* **Sync from external schedule:** The **Scheduling** integration capability allows your app's release pilot rotation to be synced from scheduling integrations like PagerDuty and Rootly. When a Scheduling integration is connected, Runway will automatically assign release pilots to releases based on your configured schedule in the integration provider.
  * **Assign release pilot based on kickoff date only:** When enabled, the assigned release pilot at the time of kickoff remains assigned as the pilot in Runway for the entire release, regardless of the external schedule's on-call assignments after kickoff. This setting is enabled by default and is only available when leveraging an external scheduling system. When disabled, Runway will update a release's pilot throughout the lifetime of its release – this facilitates mid-cycle hand-offs when one person's shift ends and another begins

{% hint style="warning" %}
If a Scheduling integration is connected, release pilot selection directly in Runway will be disabled. You must manage release pilots and overrides from your Scheduling integration directly.
{% endhint %}

* **Keep previous release pilot for hotfixes and rollbacks:** By default, Runway will reassign the same release pilot to any hotfixes or rollbacks that follow their originally assigned release. If this option is disabled, Runway will instead assign the next person in the rotation (in Runway, or an external on-call schedule if applicable) as the release pilot for any hotfixes or rollbacks.
* **Consecutive releases per pilot:** Number of consecutive releases that a given pilot should support when they come up in the rotation, not including hotfixes or rollbacks. (Not applicable to rotations set by external scheduling tools)

### Changing the pilot for a single release

A single release can be reassigned without changing the rotation order. Each upcoming release in the rotation list has an action menu with two options:

* **Replace pilot for `<version>`**: select the pilot who should fly that release. The release is assigned to that pilot, and every other release keeps the pilot it was already assigned.
* **Swap pilot for `<version>`**: select the pilot to trade turns with. Runway identifies the next upcoming release for that pilot and swaps the two. Every other release keeps the pilot it was already assigned.

{% hint style="warning" %}
You must have the **Update release pilot** permission to Replace or Swap pilots.
{% endhint %}

{% hint style="warning" %}
When the rotation is synced with an external scheduling integration, Replace and Swap are unavailable. Changes should be applied directly in the external tool, and will then be picked up by Runway on the next integration sync.
{% endhint %}