# UI-009 Provider Connections

| Field | Value |
| --- | --- |
| Route | `/admin/provider-connections` |
| Source | `ProviderConnectionResource` |
| Area / scope | Provider / integration / workspace |
| Archetype | Provider / Integration |
| Design depth | Strategic Surface |
| Repo truth | repo-verified |
| Screenshot | `specs/353-provider-connections-resolution-guidance-v1/artifacts/screenshots/ui-072-provider-connections.png` |
| Browser status | Guidance-integrated; desktop screenshot saved under the Spec 353 artifact path. |

## First Five Seconds

The surface now leads with one provider-readiness case, one dominant primary action, and only then the existing provider truth and safe secondary actions.

## Productization Review

- Decision-first: strong; list and detail now explain the primary blocker before secondary operator actions.
- Evidence-first: provider health and verification remain visible, but subordinate to the blocker and next step.
- Context: workspace-owned provider connection surface.
- Customer/auditor safety: internal/operator only.
- Diagnostics: technical details remain available without taking over the first-screen hierarchy.

## Information Inventory

Default content now includes:

- one dominant provider-readiness case
- one primary action
- provider, target scope, consent, verification, and capability truth
- grouped secondary actions under `More`
- technical details on demand

Diagnostic detail continues to explain missing permission, consent, and verification context without exposing raw provider payloads or secrets.

## Dangerous Actions

Credential rotation, disable/enable, revert, and secret mutations remain grouped and capability-gated. The new guidance layer does not introduce auto-fix or auto-consent actions.

## Scores

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

## Top Issues

1. Edit-page guidance is intentionally deferred; the primary operator journey is list/detail first.
2. Existing `More` action density remains high, even though the primary readiness CTA is now clearer.
3. Provider capability/detail language still assumes operator familiarity with Microsoft-style readiness concepts.

## Target Direction

Implemented in Spec 353 as a bounded operator-guidance layer over existing provider readiness truth. Follow-up should focus on secondary-action density, not on another provider state framework.