# Deploy apps across your organization

Create and manage organization-wide app deployments.

> #### Get early access to organization deployments.
> 
> Organization deployments is in [private preview](https://docs.stripe.com/release-phases.md). If you want to join the preview, [share your email address to request access](https://docs.stripe.com/terminal/fleet/organization-deployments.md#signup). 
### Get early access to organization deployments.

Enter your email to request access.

```bash
curl https://docs.stripe.com/preview/register \
  -X POST \
  -H "Content-Type: application/json" \
  -H "Referer: https://docs.stripe.com/terminal/fleet/organization-deployments" \
  -d '{"email": "EMAIL", "preview": "terminal_organization_deployments"}'
```


Organization deployments lets you deploy apps across your Stripe accounts from a central location. Create a single deployment to trigger account deployments in bulk, with unified monitoring and controls across all targeted accounts.

## Before you begin

Make sure that you meet these requirements:

- You have at least one Account Group configured for Terminal app sharing. Stripe configures this during organization deployments onboarding. The Account Group defines the accounts and Deploy Groups that you can include in a deployment.
- You created the [deploy groups](https://docs.stripe.com/terminal/features/apps-on-devices/deploy-in-dashboard.md#manage-deploy-groups) that you want to target for each account.
- You uploaded at least one [device asset version](https://docs.stripe.com/terminal/features/apps-on-devices/submit.md#create-device-asset-version) to an account.

## Create a deployment

Create an organization deployment in the Stripe Dashboard to roll out app versions across multiple accounts and deploy groups.

1. From the [organization dashboard](https://dashboard.stripe.com/org/dashboard), go to **Payments** > **Terminal**.
2. Click **Create deployment**.
3. Select the Deploy Groups that you want to target.
4. Choose the asset versions to install. You can use asset versions from any account in your Account Group.
5. Configure your rollout stages (for example, 10%, 50%, and 100%), mandatory install timelines, and launch app preferences.
6. Confirm and create the deployment. Stripe creates a deployment for each selected deploy group with your configured assets and settings.

## Monitor and manage a deployment

After you create a deployment, it appears in the deployments table on the overview page alongside ongoing, paused, and completed deployments. Open a deployment to view its detail page, which shows:

- Deployment configuration and rollout stage
- Aggregate progress metrics (readers served, updated, failed)
- Per-account deployment status

Use these details to decide whether to continue the rollout, pause it, resolve account-level failures, or archive deployments you no longer need.

### Control rollout progress

Use these controls to manage rollout progress:

- **Advance**: Click this when the current rollout stage is healthy and you want to move to the next stage.
- **Pause**: Click this if you see elevated failures or need time to investigate.
- **Resume**: Click this after you resolve the issue and want to continue the deployment.

### Resolve failed deployments

Use these actions to handle failed deployments:

- **Retry**: Use this when the deployment fails to create correctly or fails to transition to the next state. Retry attempts the failed operation again without changing the rollout configuration.
- **Eject**: Use this when one account can’t proceed and is blocking the rest of the organization deployment. For example, eject an account if its deployment was paused outside the organization deployment or if the account needs account-level remediation before it can continue.

### Archive deployments

Use **Archive** when a deployment is no longer active or no longer needs to appear in your main deployment views.

Archiving hides the deployment from primary views, but it doesn’t uninstall apps, change rollout stages, or affect deployment status on readers.