administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-04-25 08:07:41 +03:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

clarify docs

Browse Source
This commit is contained in:
Josh Hawkins 2025-09-11 12:23:01 -05:00
parent b1f1873bc1
commit db41d74759
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/docs/configuration/authentication.md
View File

@ -170,7 +170,7 @@ In this example:
- The `remote-role` header determines the user’s privileges: - The `remote-role` header determines the user’s privileges:
- **admin** → Full access (user management, configuration changes). - **admin** → Full access (user management, configuration changes).
- **viewer** → Read-only access. - **viewer** → Read-only access.
- **Custom roles** → Access limited to the cameras defined in `auth.roles[role]`. - **Custom roles** → Read-only access limited to the cameras defined in `auth.roles[role]`.
- Ensure your **proxy sends both user and role headers** for proper role enforcement. - Ensure your **proxy sends both user and role headers** for proper role enforcement.
**Unauthenticated Port (5000)** **Unauthenticated Port (5000)**
@ -220,7 +220,7 @@ Frigate supports user roles to control access to certain features in the UI and
### Custom Roles and Camera Access ### Custom Roles and Camera Access
Custom roles allow fine-grained control over camera access. Each role specifies an array of allowed camera names. If a user is assigned a role, they are like the **viewer** role - they can only view Live, Review/History, Explore, and Export for those cameras. Backend API endpoints enforce this server-side (e.g., returning 403 for unauthorized cameras), and the frontend UI filters content accordingly (e.g., camera dropdowns show only permitted options). The viewer role provides read-only access to all cameras in the UI and API. Custom roles allow admins to limit read-only access to specific cameras. Each role specifies an array of allowed camera names. If a user is assigned a custom role, their account is like the **viewer** role - they can only view Live, Review/History, Explore, and Export for the designated cameras. Backend API endpoints enforce this server-side (e.g., returning 403 for unauthorized cameras), and the frontend UI filters content accordingly (e.g., camera dropdowns show only permitted options).
### Role Configuration Example ### Role Configuration Example