Skip to main content
The UI Settings tab holds admin flags that shape what non-admin (internal) users can do in the dashboard, how the gateway forwards headers, and which pages internal users see. Find it at Admin Settings -> UI Settings. Each toggle writes a single flag and takes effect immediately; the Projects toggle also refreshes the page
These are proxy-wide flags set by an admin. “Internal users” means any signed-in user who is not a proxy admin. Team admins are internal users with extra powers on the teams they manage, which is why two toggles have a team-admin exemption

Access control for internal users

The two “Allow … for team admins” switches are dependent: they do nothing on their own and stay disabled in the UI until their parent “Disable …” toggle is on. Turn the restriction on first, then grant the team-admin exemption

Header forwarding (Claude Code and BYOK)

These two are independent of each other and of any deployment-configured key. Turn on only the ones you need
Forwarding provider auth headers lets a caller override the gateway’s configured key with their own for that request. Turn it on only when you intend clients to bring their own key

Experimental

Page visibility for internal users

Below the toggles, the Page Visibility control (enabled_ui_pages_internal_users) picks exactly which sidebar pages internal users can open. Leaving it unset shows the default set; selecting pages restricts internal users to just those. Admins always see every page

Setting these by API

The toggles are a thin wrapper over one admin endpoint. Each switch sends its single flag:
Send any flag from the tables above. Booleans for the toggles, and an array of page names for enabled_ui_pages_internal_users. The current values are readable at GET /get/ui_settings