Delete user notification channel

Outcome

Delete the exact user/address row without changing primary email, policy, queued events or sessions.

These examples prove local handler behavior with real isolated notification SQL and explicitly simulated identity dependencies.

Before you start

• Verify pinned identity and the exact published action. Preference/address storage permits self or platform authority; organization admin alone cannot manage another user. Organization forbid rules require authority over the exact organization.

• Discover the intended user/org independently. These storage handlers do not verify target existence and stored preference lists do not resolve effective delivery. Omitted preference org_id means global wildcard *, while replacement selects organization scope through query.org_id.

• Before replacement capture the complete previous scope, review the full intended rows and inspect the validated plan. Empty rows clears explicit rules and may permit more delivery. Replacement is sequential and can leave partial state.

• Channel verify only sets a stored flag and performs no possession challenge. Retain independent authorized ownership evidence before approving it; fixture addresses are unused and authorize no live verification or outreach.

Discover the target

topolo whoami --json
topolo apps --json
topolo actions get app_topolo_auth.user_notification_channels.delete --detail --json

Discover the authorized target user and exact organization. Read user_notification_preferences.list for each scope separately, user_notification_channels.list for stored channel_id values, or organization_notification_policy.list for the managed organization. Copy ids only from the exact selected scope. Effective delivery requires the published resolve action and delivery read-back separately.

Input fields

Effects

• Deletes only the selected user/address row; keeps primary email and independent preferences/policies.

• Queued events and sessions are unaffected.

Interpret the response

Deletes only the exact user/channel pair, returning real affected identifiers. Another user pair and repeated deletion return 404.

It does not remove primary account email, alter preference/policy rows, cancel queued messages or revoke sessions. Re-registration creates a new pending row/id and does not restore verification history.

Worked examples

These are complete raw target-handler responses, not CLI/gateway envelopes or live authorization proof. Synthetic users, organizations and unused addresses exist only in isolated fixtures. Discover real intended targets and review effects separately. Save only reviewed input as payload.json; validate and inspect the unchanged plan before an authorized call. --confirm assumes intended approval. Cookie/Bearer identities must consistently select the intended principal. Stored rows, ownership evidence, effective policy and actual delivered messages are separate outcomes. No fixture sends a message or performs an address challenge.

Delete exact selected address without modifying primary email or other users

Input · payload.json:

{
  "userId": "usr_self",
  "channelId": "nch_DUthNOwIONWASRT_"
}

CLI:

topolo actions validate app_topolo_auth.user_notification_channels.delete --data @payload.json --json
topolo actions plan app_topolo_auth.user_notification_channels.delete --data @payload.json --confirm --json
topolo actions call app_topolo_auth.user_notification_channels.delete --data @payload.json --confirm --json

MCP call after validation and plan review:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_auth.user_notification_channels.delete",
    "input": {
      "userId": "usr_self",
      "channelId": "nch_DUthNOwIONWASRT_"
    },
    "confirm": true
  }
}

Captured local handler response · HTTP 200:

{
  "success": true,
  "message": "Notification channel deleted",
  "data": {
    "userId": "usr_self",
    "channelId": "nch_DUthNOwIONWASRT_"
  },
  "timestamp": "2026-10-02T00:00:00.000Z"
}

Delete another discovered address after separately approved selection

Input · payload.json:

{
  "userId": "usr_self",
  "channelId": "nch_mPQVYgYmwm8cHAjT"
}

CLI:

topolo actions validate app_topolo_auth.user_notification_channels.delete --data @payload.json --json
topolo actions plan app_topolo_auth.user_notification_channels.delete --data @payload.json --confirm --json
topolo actions call app_topolo_auth.user_notification_channels.delete --data @payload.json --confirm --json

MCP call after validation and plan review:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_auth.user_notification_channels.delete",
    "input": {
      "userId": "usr_self",
      "channelId": "nch_mPQVYgYmwm8cHAjT"
    },
    "confirm": true
  }
}

Captured local handler response · HTTP 200:

{
  "success": true,
  "message": "Notification channel deleted",
  "data": {
    "userId": "usr_self",
    "channelId": "nch_mPQVYgYmwm8cHAjT"
  },
  "timestamp": "2026-10-02T00:00:00.000Z"
}

Verify the result

• Read the exact user channels and require acknowledged channelId absent, with other rows retained.

• Resolve intended delivery separately because primary email or other routes may remain. No cancellation or external delivery proof follows from deletion.

Errors and recovery

Platform authority still requires the exact channel/user pair for deletion

Captured local refusal · HTTP 404:

{
  "input": {
    "userId": "usr_other",
    "channelId": "nch_DUthNOwIONWASRT_"
  },
  "response": {
    "success": false,
    "error": {
      "message": "Notification channel not found",
      "code": "NOT_FOUND",
      "details": null,
      "timestamp": "2026-10-02T00:00:00.000Z"
    }
  }
}

Repeated address deletion is not a second success

Captured local refusal · HTTP 404:

{
  "input": {
    "userId": "usr_self",
    "channelId": "nch_DUthNOwIONWASRT_"
  },
  "response": {
    "success": false,
    "error": {
      "message": "Notification channel not found",
      "code": "NOT_FOUND",
      "details": null,
      "timestamp": "2026-10-02T00:00:00.000Z"
    }
  }
}

Published recovery guidance

• state_conflict (HTTP 409): Read the current resource state, reconcile the intended change, and retry only if still valid.

• AUTH_ERROR (HTTP 401): Verify pinned identity. If authenticated, respect self/platform user authority or exact organization management denial; organization ownership alone does not authorize another user address/preferences. Do not assume OAuth expiry or change context automatically.

• VALIDATION_ERROR (HTTP 400): Correct the reported fields only. Use unique event/channel pairs and valid channel-specific addresses. Validate and review the exact complete replacement again before approval.

• NOT_FOUND (HTTP 404): Refresh the target user channels list. A row for another user is not authorized by a known channel id; repeated delete is already absent, not a new successful deletion.

• SERVER_ERROR (HTTP 500): Preserve the result and read the exact stored scope before any new write. A replacement may have deleted old rules and inserted only some new ones; review finishing the intended set or restoring the captured set as a new approved replacement.

Recovery boundaries

Separately review re-registration with captured nonsecret channel/address/label/metadata. It creates a new pending row/id; prior verification timestamp and delivery history are not restored. Independently establish ownership before any new verification flag action.

Discovery and evidence

This record belongs to app_topolo_auth. Fixtures prove actual NotificationPreferencesController and AuthController authority, validation, canonical notification SQL, duplicate/address identity and sequential replacement failure boundaries. Authenticated identities and unused targets/addresses are simulated and second-insert SQL failures injected. No live storage, ownership challenge, notification, deployment or production publication is proved.