403 Erasure requires an org admin

GDPR erasure is restricted by ROLE as well as by scope, and the acting member does not hold a qualifying role.

Retrying will not help

What causes it

• The key carries `contacts.erase` but is attributed to a REP.

How to fix it

• Recreate the key while signed in as a MANAGER, ADMIN or OWNER. The `contacts.erase` scope alone is deliberately not sufficient: erasure is irreversible, so it is gated on a person as well as a token.

Example response

HTTP/1.1 403
Content-Type: application/problem+json

{
  "type": "https://sealdeal.ai/errors/erasure-forbidden",
  "title": "Erasure requires an org admin",
  "status": 403,
  "detail": "..."
}

`type` is stable and safe to branch on in code. `detail` is specific to your request and is the field to read for the particulars; its wording may change.