From adfa9ec1396a35d2aa9878cb525b8380c56cecfa Mon Sep 17 00:00:00 2001
From: Lars <Lars@stommer.de>
Date: Fri, 20 Mar 2026 11:57:26 +0100
Subject: [PATCH] fix: AdminUserRestrictionsPage - use same tier limits
 fallback as TierLimitsPage
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Use `null` (unlimited) instead of `feature.default_limit` when no
tier_limits entry exists. This fixes Selfhosted tier showing 0
instead of ∞ for features like AI analysis.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 frontend/src/pages/AdminUserRestrictionsPage.jsx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/frontend/src/pages/AdminUserRestrictionsPage.jsx b/frontend/src/pages/AdminUserRestrictionsPage.jsx
index 6376145..72e6555 100644
--- a/frontend/src/pages/AdminUserRestrictionsPage.jsx
+++ b/frontend/src/pages/AdminUserRestrictionsPage.jsx
@@ -62,7 +62,8 @@ export default function AdminUserRestrictionsPage() {
       const limits = {}
       features.forEach(feature => {
         const key = `${userTier}:${feature.id}`
-        limits[feature.id] = limitsMatrix.limits[key] ?? feature.default_limit
+        // Use same fallback logic as TierLimitsPage: undefined → null (unlimited)
+        limits[feature.id] = limitsMatrix.limits[key] ?? null
       })
       setTierLimits(limits)