> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Devin environment rollout health

> Use Devin's Enterprise Rollout page to monitor blueprint adoption, build health, and environment readiness across organizations.

The Enterprise **Rollout** page shows environment health across the organizations in your enterprise and helps you find organizations that need a blueprint or a build fix.

For the environment model behind these metrics, see [Enterprise environment management](/enterprise/environment-management/overview) and [declarative environment configuration](/onboard-devin/environment/blueprints).

## Summary metrics

The page summarizes:

| Summary card | Meaning |
| - | - |
| **Organizations** | Organizations in this enterprise. |
| **Build health** | Shown as “passing / total”: organizations whose latest environment build fully succeeded, out of those with builds. The remainder completed with failed steps. |
| **Build success rate** | Percentage of builds across the enterprise in the past 7 days that fully succeeded. Builds that completed with failed steps count against it. |
| **Unconfigured organizations** | Organizations with no configured repositories and no organization-level configuration. |
| **Needs attention** | Configured organizations with 3 or more consecutive failed builds, or with no usable snapshot. Select the card to filter the organization table to these organizations. |

## Organization health

The organization table includes:

| Column | Meaning |
| - | - |
| **Organization** | Links to that organization's environment settings. |
| **Configured repositories** | Count of declaratively configured repositories, with an icon marking organizations that also have organization-level configuration. |
| **Latest build** | A Success, Partial, or Failed badge, or a dash when there is no build. A **No snapshot** badge marks organizations that need attention because they have no usable snapshot and fall back to the base image. |
| **Consecutive failures** | Number of failed builds since the last successful or partial build. Highlighted once it reaches 3. |
| **Last usable build** | Relative time of the last build that produced a snapshot sessions can boot from, or “Never”. Partial builds (completed with failed steps) count. |

By default, the table sorts organizations that need attention first, then by latest build status (Failed, Partial, no build, Success), then by consecutive failures. Use the search box to find an organization, or switch the filter from **All organizations** to **Needs attention**.

Use the table to identify:

* Organizations with no blueprint or declarative repositories.
* Organizations with `partial` or `failed` builds.
* Organizations that need attention, or whose last usable build is stale.

## Phased blueprint adoption

Use the health data to adopt blueprints in controlled phases:

### 1. Validate the enterprise baseline

Create and validate an enterprise-tier base blueprint with the tools, runtimes, certificates, and shared configuration every organization needs. Confirm that its build succeeds and that a representative session can use the resulting environment.

See [Enterprise environment management](/enterprise/environment-management/overview) for the blueprint hierarchy and shared configuration guidance.

### 2. Add organization and repository configuration

After the enterprise baseline is healthy, configure organization blueprints for team-level tools and repository blueprints for project-specific dependencies and commands. Start with representative organizations and repositories, then expand to the rest of the enterprise.

Use [environment blueprints](/onboard-devin/environment/blueprints) to author and review the configuration.

### 3. Monitor build health

Return to the Rollout page after each adoption phase. Investigate organizations with missing blueprints, partial or failed builds, consecutive failures, and stale last-usable-build timestamps. Fix the relevant enterprise, organization, or repository blueprint, then confirm the next build returns to a healthy status.

<Tip>
  Treat a passing build as a checkpoint, not the end of validation. Start a real Devin session for representative repositories and verify that tools, dependencies, network access, and project commands work as expected.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.