---
id: SCR-PFM-TNL-001
title: Request deletion dialog
route: /hq/tenants/{id} (dialog opened from the HQ workspace detail; 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 (Request deletion dialog); services-platform:docs/hq/rhythm-hq-plan.md#§D4,
  §D14 (deletion screens deferred)
implementation_evidence: not-investigated
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
purpose: Help authorized staff request removal of a disabled workspace after confirming the selection and recording
  a reason.
supports:
- JNY-PFM-TNL-004
- JNY-PFM-TNL-002
- CAP-PFM-TNL-013
- CAP-PFM-TNL-015
permission: platform.tenants.deletion-request
entry_from:
- SCR-PFM-SEC-027 HQ workspace detail, when the workspace is disabled and active or provisioning failed
exits_to:
- SCR-PFM-TNL-003 Deletion request detail of the new request
- SCR-PFM-SEC-027 on cancel
displays:
- field: Workspace and customer identity
  source: getHqTenant
- field: Current business and lifecycle standing
  source: DOM-PFM-TNL-001 lifecycle state; getHqTenant
- field: Applicable wait from activation history and disposable standing
  source: DOM-PFM-TNL-001 first activation time and disposable designation
- field: Name supplied for confirmation
  source: person
- field: Request explanation
  source: person
- field: Choice to remove the final customer
  source: person
- field: Optional disposable wait
  source: person
actions:
- label: Submit deletion request
  operation_id: requestTenantDeletion
  permission: platform.tenants.deletion-request
  confirm: true
states:
- loading
- error
- read-only
- inactive
validation:
- BR-CAP-PFM-TNL-013-01
- BR-CAP-PFM-TNL-013-03
- BR-CAP-PFM-TNL-013-04
- BR-CAP-PFM-TNL-013-05
- BR-CAP-PFM-TNL-013-07
- BR-CAP-PFM-TNL-013-08
- BR-CAP-PFM-TNL-013-09
- BR-CAP-PFM-TNL-013-11
- BR-CAP-PFM-TNL-018-08
patterns:
- design-system Dialog with a destructive confirmation
- typed-name confirmation field that does not echo the expected answer
- form field errors from the API refusal
- no immediate delete control anywhere
evidence:
- 'services-platform at ad3f6a65: docs/tenants/console-contract.md; docs/hq/rhythm-hq-plan.md §D4, §D14; modules/tenants/aws/api/tenant-deletion-requests.{routes,schemas}.ts.'
- 'rhythm-v2-docs: specs/platform/security/design/screens/SCR-PFM-SEC-027 (the built HQ workspace detail carries
  no lifecycle controls).'
- 'FND-PFM-TNL-038: source registration cannot establish absence of a console component.'
inference: []
controls: [TC-AVL-001, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-005, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-DAT-004, 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-002, TC-PI-001, TC-PI-002, TC-PI-003, 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]
---

# Request Deletion Dialog

## What the Screen Is For

This proposed dialog records a staff decision to remove a workspace. The requester confirms the workspace name and explains the decision before the waiting period starts.

## What It Shows and Lets People Do

Show the workspace and customer, current standing, and the applicable wait. The usual wait is thirty days; a workspace with no recorded activation waits one day, and a disposable workspace outside Production can use minutes. Collect the exact workspace name, a reason, the optional choice to remove the customer with its last workspace, and any permitted disposable wait. Submit the reviewed workspace version with the request and open its detail after success.

## States and Errors

Enable submission only for a disabled workspace in active or failed-provisioning lifecycle. Explain service refusals for selection, reason, version, protected standing, children, locking or an existing request. Retain the entered values while the person resolves a refusal. Immediate deletion has no control.

## Patterns It Must Respect

The documented requirement calls for a destructive confirmation and field errors. The route and component pattern are proposals: no registered console source establishes a built dialog. The future confirmation field must require the person to supply the name.