ryan-crabbe-berri 6a248be76f fix(ui): gate team guardrail admin actions behind proxy admin role ... Internal (non-admin) users could see Approve/Reject buttons and the forward-key / header edit controls on the Submitted Guardrails tab even though the backend approve, reject and update endpoints are PROXY_ADMIN only and reject those calls. The controls now render only for a true proxy admin, gated on isProxyAdminRole so Admin Viewer (which the backend also rejects) no longer sees them either. Non-admin team members keep full read visibility: submission status, team, configured headers and the forward-key state (shown as a read-only label instead of a toggle), so they can still see the status of a guardrail they submitted and the guardrails attached to their team. userRole is threaded from GuardrailsPanel into TeamGuardrailsTab to drive the gating		2026-07-23 14:28:24 -07:00
..
litellm-dashboard	fix(ui): gate team guardrail admin actions behind proxy admin role	2026-07-23 14:28:24 -07:00
Dockerfile	feat: add componentized proxy deployment with gateway, backend, ui, and migrations (#27557)	2026-05-16 09:25:17 -07:00
nginx.conf	fix(ui): serve /ui/assets from the nginx image instead of SPA fallback (#34066)	2026-07-21 09:22:02 -07:00