Skip to content

Security Alert Acknowledgment Not Permitted

URI: https://docs.ankatech.co/errors/security-alert-acknowledgment-not-permitted
HTTP Status: 403 Forbidden

When you see this

A tenant's security alert was addressed to the platform's acknowledgment (POST /api/v3/admin/platform/security-alerts/{alertId}/acknowledgment). The platform reads every tenant's alerts, read-only, but never acknowledges them, on every deployment type: only the tenant's own administrators do. Nothing was changed.

Common Causes

  • The alert was listed with scope=TENANT on the platform plane, where every item reads acknowledgeable: false, and was then acknowledged there.

Response Example

{
  "type": "https://docs.ankatech.co/errors/security-alert-acknowledgment-not-permitted",
  "title": "Security Alert Acknowledgment Not Permitted",
  "status": 403,
  "detail": "This security alert belongs to a tenant and is acknowledged only by that tenant's administrators. Nothing was changed.",
  "instance": "/api/v3/admin/platform/security-alerts/5c9e2f14-8b3a-4d71-9e6c-2a1f7d0b4e83/acknowledgment",
  "timestamp": 1760951700,
  "extensions": {
    "requestId": "4e2a9c71-0b3d-4f58-a6e1-9d7c2b5f8e30"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. This is an Admin API body, so the correlation identifier is extensions.requestId; see Error Index & Overview.

How to Resolve

  1. Ask an administrator of the tenant to acknowledge the alert on the tenant's own security alerts screen.
  2. Acknowledge on the platform plane only the platform's own alerts (scope=PLATFORM).

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.