GRI-1978: panel users, roles and permission-gated nav (campus test scope) #173
No reviewers
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage!173
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/GRI-1978-panel-users-permissions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Panel screens for users, roles and permissions, scoped to the campus
production test (chief of staff's release note, 2026-11-13):
UsersScreen: list, create, edit and delete users for admins(
users_manage). Role is one of the fixed set (Admin,Campus Editor) — there is no group CRUD yet, matching the server. Anon-admin group's user is scoped to one campus or "All campuses";
an admin group always sees every campus.
DashboardScreen: the Devices/IP rules/Media/Playlists/Users/Settings tabs and the routes behind them are gated by the signed-in
user's permissions. IP rules needs
devices_approve, Settings andUsers need
settings_manage/users_manage— a Campus Editor seesneither tab, and typing the URL directly shows "You do not have
permission to view this page" instead of the screen.
SessionUsernow carriesisAdmin,campusIdandpermissions,parsed from the server's
UserView(is_admin,campus_id,permissions— GRI-1970, already indev).campusApianduserGroupsApimodules back thecreate/edit form's campus and role selects.
API tokens are explicitly out of scope for this release (not needed
for the one-campus test); left for a follow-up.
Testing
No QA-authored frontend tests exist for this screen; this repo's
convention has the frontend engineer write vitest tests alongside
each screen (GRI-1764), with QA owning backend acceptance tests
(e.g. GRI-1971).
UsersScreen.test.tsxandDashboardScreen.test.tsxcover: loading/empty/error states, create/edit/delete, duplicate
email, an admin-group campus refusal, and the permission-gated nav
and routing.
scripts/local-gates.sh --frontend-only: prettier, oxlint(
--deny-warnings),tsc -b, the full vitest suite (48 passed) andvite buildall passed.I could not drive the app in a real browser in this sandbox (no
Playwright/Chromium available, no network to fetch one) — the states
above are verified through jsdom-rendered component tests with real
user interaction (
@testing-library/user-event), not a screenshot.Closes #52.