Story: Build the retire or reset tenant journey — the remaining work
Table of Contents
This page documents a story in Sprint 30, carried unfinished from Sprint 28 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
Retire or reset a tenant runs end to end: a tenant administrator suspends a tenant, terminates, deprovisions and purges it, and resets a party's tenant, and the roster's row menu offers Retire or reset instead of showing it as not built.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 30 |
| Now | Not yet started. Split from Build the retire or reset tenant journey, which closed in sprint 28 with its done tasks. |
| Waiting on | Nothing. |
| Next | Triage into a sprint. |
| Last touched | 2026-11-08 |
3. Acceptance
- Suspend has its operation and its subject over
iam::tenants:suspend, and a suspended tenant cannot sign in. - Terminate, deprovision and purge each have a subject over their SQL
function (
ores_iam_terminate_tenant_fn,ores_iam_deprovision_tenant_fn,ores_iam_purge_tenant_fn). - The party-level reset has a subject over
ores_iam_reset_tenant_fn. - The roster's row menu offers Retire or reset, and the screen does not offer what the server cannot do.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Land the retire and reset operations | BACKLOG | Build the server path behind the Retire or reset a tenant journey: a suspend operation with its subject, subjects for terminate, deprovision and purge, a subject for the party-level reset, and the roster's row menu item. |
5. Decisions
- Split from Build the retire or reset tenant journey on 2026-10-24 at sprint 28 close. The acceptance above is copied from that story; its done tasks are recorded there.
6. Out of scope
- The unguarded system-tenant delete and the sign-in path that ignores a suspended tenant, which are Fix the security defects the ores.iam clean-up recorded.