# UI-010 Managed Environments

| Field | Value |
| --- | --- |
| Route | `/admin/workspaces/{workspace}/environments` |
| Source | `ManagedEnvironmentsLanding`, `ManagedEnvironmentLinks` |
| Area / scope | Workspace / environment portfolio |
| Archetype | Workspace / Tenant Context |
| Design depth | Strategic Surface |
| Repo truth | repo-verified |
| Screenshot | `-` |
| Browser status | Reached in local browser with workspace `3`; implementation pass verified long-name layout behavior. |

## First Five Seconds

The page is the workspace-scoped environment portfolio entry point. Operators need to identify the correct environment quickly before drilling into environment-owned dashboards, evidence, backup, restore, findings, or access surfaces.

## Productization Review

- Decision-first: improved by presenting each environment as a full-width selectable row/card with stable identity and status.
- Evidence-first: intentionally light; this is a portfolio chooser, not a posture dashboard.
- Context: workspace name and environment count remain visible above the list.
- Customer/auditor safety: operator-facing only; no customer evidence copy is introduced.
- Diagnostics: raw diagnostics stay out of the default surface.

## Information Inventory

Default-visible content includes workspace identity, environment count, environment name, provider/external identifier, and lifecycle status. Add-environment and switch-workspace actions are available in the header. Empty state remains bounded to onboarding and workspace switching.

## Dangerous Actions

No destructive action is present. Opening an environment is a navigation action; adding an environment routes to onboarding and does not mutate from this page.

## Scores

| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
| ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 |

## Top Issues

1. No portfolio-level health, sync, or backup posture signal is shown yet.
2. No search/filter exists for larger MSP portfolios.
3. Static screenshot evidence is still absent from the durable audit artifact set.

## Target Direction

Keep the current runtime as a robust enterprise baseline for environment selection. A later portfolio spec can add search/filter and lightweight posture signals once the page carries enough environments to justify that added interaction surface.