Repository navigation
ADR 0018
github-actions[bot] edited this page Nov 21, 2026
·
1 revision
Status: superseded · Built: done · Date: 2026-11-08 · Superseded by: 0035
Banning, editing and impersonation are left for later.
Apps that use the backend kit keep their users in the auth schema of their own database
(ADRs 0015 and 0016). The operator needs to see those users and remove one when necessary,
without each app building an admin screen.
-
The agent reads the
authtables directly, as their owner. Its routes, with strict schemas:-
GET /apps/:name/users(paged): id, created, last seen and whether the user is a guest; -
DELETE /apps/:name/users/:id: the user's sessions and the app's rows go through the foreign-key cascades.
-
- The dashboard shows a Users tab per app, with a confirmation before deleting. It still talks only to the agent and keeps no data.
- An app database without the
authschema is shown as "not using the kit".
- It works while the app is down.
- It depends on the kit's table layout, which Spotcraft migrates itself, so the agent always knows that layout.
- Deleting is the only moderation tool until banning is added.
Published from docs/. Edit the files there; changes here are overwritten.