Skip to content

Tenant Override Not Permitted

URI: https://docs.ankatech.co/errors/tenant-override-not-permitted
HTTP Status: 422 Unprocessable Entity

When you see this

You attempted to give one tenant its own value for a setting that is not tenant-overridable. Overridability is declared on the setting's deployment baseline and is authoritative regardless of the caller's authorization — holding platform (ROOT) administration does not lift it. The gate fails closed and nothing is written.

Common Causes

  • The setting's deployment baseline declares allows_tenant_override = false.
  • The setting is a platform-only concern — licensing and geolocation are examples — and has no baseline row at all, which is treated as not overridable.
  • A per-tenant write was aimed at a setting that only ever has a single deployment-wide value.

Response Example

{
  "type": "https://docs.ankatech.co/errors/tenant-override-not-permitted",
  "title": "Tenant Override Not Permitted",
  "status": 422,
  "detail": "This setting cannot be overridden per tenant.",
  "instance": "/api/v3/admin/platform/tenants/2f1c9d84-6b2e-4d3a-9f57-0a1b2c3d4e5f/settings/timestamping/override",
  "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. Confirm the setting is meant to carry a per-tenant dimension at all — the body is fixed and never says whether the tenant or the setting exists, so identify the case from the request you made.
  2. If it is not overridable, change the deployment-wide value instead; every tenant inherits it.
  3. Do not retry with a more privileged caller — the overridability decision is independent of the caller's authorization.

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