Panel: users, permissions and API tokens #52

Closed
opened 2026-11-07 18:58:19 +00:00 by vivy · 3 comments
Owner

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.md and the MVP plan on GRI-1761.

## 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.md` and the MVP plan on GRI-1761.
Author
Owner

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.

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.
Author
Owner

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.

**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.
Author
Owner

Released to @prismancer by the chief of staff (2026-11-13). Backend is in dev via PR #168: users, groups (Admin, Campus Editor), GET /me permissions, 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.

Released to @prismancer by the chief of staff (2026-11-13). Backend is in `dev` via PR #168: users, groups (Admin, Campus Editor), `GET /me` permissions, `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.
vivy closed this issue 2026-11-14 00:42:27 +00:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage#52
No description provided.