diff --git a/docs/docs/configuration/authentication.md b/docs/docs/configuration/authentication.md
index dcd5d84a1..0d80d80ce 100644
--- a/docs/docs/configuration/authentication.md
+++ b/docs/docs/configuration/authentication.md
@@ -232,19 +232,7 @@ proxy:
 
 ## Role mapping
 
-In some environments, upstream identity providers (OIDC, SAML, LDAP, etc.) do not pass a Frigate-compatible role directly, but instead pass one or more group claims. To handle this, Frigate supports a `role_map` that translates upstream group names into Frigate's internal roles (`admin`, `viewer`, or custom).
-
-<ConfigTabs>
-<TabItem value="ui">
-
-Navigate to <NavPath path="Settings > System > Proxy" /> and configure the role mapping under the header mapping settings.
-
-| Field                         | Description                                                                                                                          |
-| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| **Header mapping > Role map** | Maps upstream group names to Frigate roles. Each Frigate role (`admin`, `viewer`, or custom) maps to a list of upstream group names. |
-
-</TabItem>
-<TabItem value="yaml">
+In some environments, upstream identity providers (OIDC, SAML, LDAP, etc.) do not pass a Frigate-compatible role directly, but instead pass one or more group claims. To handle this, Frigate supports a `role_map` that translates upstream group names into Frigate's internal roles (`admin`, `viewer`, or custom). This is configurable via YAML in the configuration file:
 
 ```yaml
 proxy:
@@ -262,9 +250,6 @@ proxy:
         - operators
 ```
 
-</TabItem>
-</ConfigTabs>
-
 In this example:
 
 - If the proxy passes a role header containing `sysadmins` or `access-level-security`, the user is assigned the `admin` role.