---
id: SCR-PFM-TNL-003
title: Deletion request detail
route: /hq/deletion-requests/{requestId} (route assumed)
surface: console
product_area: platform
module: tenant-lifecycle
revision: 1
status: draft
design_intent: confirmed
origin: services-platform:docs/tenants/console-contract.md#Screens (Deletion request detail), Behaviour the console
  must respect; services-platform:docs/tenants/tenant-lifecycle-plan.md#§5.4, §5.8
implementation_evidence: not-investigated
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
purpose: Help staff inspect a deletion, preserve the workspace before execution, recover stopped jobs and review
  the result.
supports:
- JNY-PFM-TNL-004
- CAP-PFM-TNL-014
- CAP-PFM-TNL-015
- CAP-PFM-TNL-016
- CAP-PFM-TNL-017
- CAP-PFM-TNL-018
permission: platform.tenants.deletion-read
entry_from:
- SCR-PFM-TNL-002 Deletion requests list
- SCR-PFM-TNL-001 after a request is made
- a deletion notice link
exits_to:
- the shared job page of the watcher or purge job
- SCR-PFM-SEC-027 HQ workspace detail while the workspace exists
displays:
- field: Request standing, copied identity and explanation
  source: getTenantDeletionRequest
- field: Fixed wait and eligibility
  source: getTenantDeletionRequest
- field: Recorded hold, release and cancellation facts
  source: getTenantDeletionRequest
- field: Notice obligations and delivery outcomes
  source: getTenantDeletionRequest (notices)
- field: Watcher and purge references; separately read job snapshots
  source: getTenantDeletionRequest (references); shared job reads (snapshots)
- field: Accumulated removal counts and verification
  source: getTenantDeletionRequest
- field: Operator-safe failure explanation
  source: getTenantDeletionRequest
actions:
- label: Pause deletion
  operation_id: holdTenantDeletionRequest
  permission: platform.tenants.deletion-hold
  confirm: true
- label: Resume held deletion
  operation_id: releaseTenantDeletionRequest
  permission: platform.tenants.deletion-hold
  confirm: true
- label: Call off deletion
  operation_id: cancelTenantDeletionRequest
  permission: platform.tenants.deletion-cancel
  confirm: true
- label: Restart stopped watcher
  operation_id: resumeTenantDeletionSchedule
  permission: platform.tenants.deletion-request
  confirm: true
- label: Retry failed removal
  operation_id: retryTenantPurge
  permission: platform.tenants.deletion-request
  confirm: true
states:
- loading
- error
- read-only
- inactive
validation:
- BR-CAP-PFM-TNL-014-01
- BR-CAP-PFM-TNL-014-02
- BR-CAP-PFM-TNL-014-03
- BR-CAP-PFM-TNL-014-04
- BR-CAP-PFM-TNL-014-05
- BR-CAP-PFM-TNL-014-06
- BR-CAP-PFM-TNL-016-07
- BR-CAP-PFM-TNL-017-12
- BR-CAP-PFM-TNL-015-05
patterns:
- record detail page with a status header
- design-system Dialog for each action with a reason field
- notice history table
- links to the shared job page
- Standard layout
evidence:
- 'services-platform at ad3f6a65: docs/tenants/console-contract.md; modules/tenants/aws/api/{tenant-deletion-requests.routes,
  tenant-deletion-request-api-mapper}.ts; services/deletion/{deletion-holds, operator-recovery}.ts.'
- 'FND-PFM-TNL-047: detail adds notices but no job snapshots.'
- 'FND-PFM-TNL-038: source registration cannot establish absence of a console component.'
inference: []
controls: [TC-AVL-001, TC-AVL-002, TC-AVL-003, TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-005, TC-AZ-006, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-DAT-004, TC-DAT-005, TC-DAT-006, TC-DAT-007, TC-IAM-001, TC-IAM-002, TC-IAM-003, TC-IAM-004, TC-IAM-005, TC-IAM-006, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-MON-001, TC-MON-002, TC-MON-003, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-VEN-001, TC-VEN-002, TC-VEN-003]
---

# Deletion Request Detail

## What the Screen Is For

This proposed page brings one deletion decision and its progress together. Staff can preserve the workspace while the decision is reversible, then follow removal and inspect the retained outcome.

## What It Shows and Lets People Do

Read the request’s copied identity, reason, dates, action facts, failure summary, removal counts and verification. Detail includes notice records and job references; job snapshots require the shared job reads. Hold, release and cancel submit a reason and the reviewed request version under their respective permissions. Schedule resume and purge retry need deletion-request authority, but their current routes take neither a reason nor a version.

## States and Errors

Hide preservation actions once execution starts, and explain a race that the service refuses because destruction has begun. Reload after a stale-version refusal. Offer schedule recovery for an eligible stopped watcher and purge retry for a failed removal. Completion keeps the page readable without preservation actions; a missing external ledger can still require operational recovery.

## Patterns It Must Respect

The documented detail requirement uses confirmation for consequential actions and links to shared job inspection. Layout, dialogs and a notice table remain proposed patterns because the console implementation is outside the read scope. The service cannot currently fulfill a requirement that every action submits a reason and version.