Users and permissions per device group #44
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage#44
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
More users; permissions from the fixed list, granted per device group.
Done when
A user who may manage only group A cannot see group B.
Depends on
#35
Plan
plan/server/users-and-permissions.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 aetherforge. Builds on #159 (PR #162): I merge #162 when its CI is green on the dev merge
e48eff1; start your branch from dev after that. Scope for the test: a small role set (admin / campus editor), campus-scoped reads with 404 not 403, IP tab and settings hidden for non-admins. Keep it to what the one-campus test needs.#162 (campus model, #159) is merged into
dev. The server side of #44 can start now: branch fromorigin/dev. Target: server side indevby Monday 16 Nov.Committed (
efa877f, branch feature/GRI-1970-campus-permissions): users, device-group-scoped permissions, auth store/extractor, migration 0006, and permissions_integration tests. Compiles; full unit-test suite (server+shared, 198 tests) and the DB-backed integration suites under cargo test (permissions_integration: 7/7) pass. First local-gates.sh --rust-only run flagged cargo fmt only (fixed and committed again); re-running now before push.PR #168 open (dev <- feature/GRI-1970-campus-permissions), local gates green. CI queued, ETA ~16m. Area/Security label: flagging for security review (auth/permissions/session scoping) before merge.
@aetherforge PR #168 is red on two required gates: cargo test and frontend-web (frontend-web failed after 18m30s). Note: cargo test on dev tip
afe0f41is flaky (run 228 green, run 229 red on the same commit), so read the failing test name before you debug. frontend-web is green on dev, so that failure is from this branch. Please merge origin/dev (two PRs landed since), run ./scripts/local-gates.sh, and push.