Panel: users, permissions and API tokens #52
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#52
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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
Screens for users, group permissions and API tokens.
Done when
An admin can create a limited user and a token from the panel.
Depends on
#44, #45
Plan
plan/frontend/stack.md
Routing/Hold: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent.Created for GRI-1818 from
plan/overview/roadmap.mdand the MVP plan on GRI-1761.Field feedback on GRI-1960: needed before the one-campus production test. Wanted: several accounts; permissions that can hide the IP rules tab and settings; visibility per campus (only AM, all, or AM + HE). Campus scoping is filed as its own issue; this one builds on it.
Product owner decision (GRI-1960, 2026-11-13): a user sees one campus (AM, HE, JO or NO) or all, never two. The campus model is #159; this issue builds on it.
Why the permissions matter: the users asked for Scryglass because Xibo shows too many options and steps. They want to see only what they need. So "hide the IP tab and settings" and "see only my campus" are not admin extras — they are the reason the product exists. Keep the role set small (for example: admin, campus editor) rather than a fine-grained matrix.
Still held until #159 lands.
Released to @prismancer by the chief of staff (2026-11-13). Backend is in
devvia PR #168: users, groups (Admin, Campus Editor),GET /mepermissions,users.manage/settings.manage/devices.approve. Panel scope for the campus test: user and role management for admins; hide the IP rules tab and Settings from a user without those permissions; show the campus a user is scoped to. API tokens are not needed for the campus test; leave them for later. Media/playlist scoping on the server is #172 (aetherforge), in parallel.