Skip to content

v0.14.0

Choose a tag to compare

@github-actions github-actions released this 20 Sep 22:31
91859ba

Per-server permissions: decide what each operator or viewer may do on each server, or hide a
server from them entirely. Closes #43.

Added

  • Per-server permissions (#43). Settings → Permissions shows every operator and viewer against
    every server. Click a cell to pick what that user may do there: view, power, console, players,
    content, backups, files, settings, delete. A role stays the default everywhere, so a viewer can be
    given power and console on one server while staying read-only on the rest, and an operator can lose
    delete on the server that matters. Turning everything off hides the server from that user
    completely: it leaves their sidebar, dashboard, backups, schedules, activity, updates, modpacks,
    live status, tasks, and blueprints, and a direct link, API call, or console socket answers "not
    found". A reference below the grid opens each permission into what it allows, what it does not,
    and the exact routes it unlocks. Existing installations are unchanged until an admin edits a cell.
    Thanks @RandomGuy908 for the request.

Internal

  • One module, services/permissions.js, answers "may this user do X on server Y" for the API,
    pages, WebSockets, map proxy, schedules, backups-by-id, blueprints, tasks, and world targets. A
    structural test walks the live API and page router stacks and fails the build if a server-scoped
    write route, sub-router mount, or page ships without a permission gate.
  • The user_server_permissions table from the very first migration is now in use; no schema change.