Not an Eligible Quorum Approver

URI: https://docs.ankatech.co/errors/quorum-approver-not-eligible
HTTP Status: 403 Forbidden

When you see this

The caller is not an eligible approver of this request: an approver is an active member of the tenant holding the quorum approve scope there now. Eligibility is counted on every decision, so an approver suspended, removed or de-scoped since the request was made no longer counts. A workload identity is never an approver.

Quorum (M-of-N) approval is described in Quorum Approval^*.

Common Causes

• The caller lacks admin.tenant.quorum.approve (or admin.platform.quorum.approve on the deployment plane).
• The caller's membership is suspended.
• The caller is a workload identity: a workload may request, never decide.

Response Example

{
  "type": "https://docs.ankatech.co/errors/quorum-approver-not-eligible",
  "title": "Not an Eligible Quorum Approver",
  "status": 403,
  "detail": "The caller is not an eligible approver for this request: an approver is an active member of the tenant holding the quorum approve scope there.",
  "instance": "/api/v3/admin/tenants/7d2f4a10-9c31-4b8e-a5d6-2f11c0b47e93/quorum/requests/9b1c2d3e-4f5a-4b6c-8d7e-0f1a2b3c4d5e/approve",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

1. Decide the request as a person who holds the approve scope.
2. If no one does, give a role carrying it to another active member.

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