Admin

Every route on this page is under /api/admin/* and requires the signed-in user’s role to be admin. See Admin for the settings page these back.

Users

GET /api/admin/users

Response: { "users": [{ "id": "...", "email": "...", "name": "...", "color": "bg-blue-500", "role": "user", "disabledAt": null, "createdAt": "..." }] }

POST /api/admin/users

Creates a user and their Personal workspace. There’s no public sign-up — this is the only way a new account gets created after /setup.

Request body

Response: 201 with the new user (not wrapped): { "id": "...", "email": "...", "name": "...", "color": "...", "role": "user" }.

PATCH /api/admin/users/:userId

Request body — all optional:

Response: { "ok": true }

DELETE /api/admin/users/:userId

Deletes the user and, since a workspace’s createdBy cascades, every workspace they created — including shared ones other people are members of, and all logs, tags, tasks, and attachments in those workspaces. There’s no confirmation at the API layer; the UI is what asks twice.

Response: { "ok": true }

Workspaces

GET /api/admin/workspaces

Every workspace on the instance, with its member list — unlike GET /api/workspaces, which only returns the signed-in user’s own.

Response

{
  "workspaces": [
    { "workspace": { "id": "...", "slug": "platform-team", "name": "Platform Team", "color": "bg-violet-500", "icon": "server", "kind": "shared", "templateMode": "today_only", "createdBy": "...", "createdAt": "..." }, "members": [{ "userId": "...", "role": "owner" }, { "userId": "...", "role": "member" }] }
  ]
}

POST /api/admin/workspaces

Creates a shared workspace. Personal workspaces are never created through this route — they’re created automatically alongside a user.

Request body

Response: 201 with the new workspace (not wrapped).

PATCH /api/admin/workspaces/:workspaceId

Renames a workspace or changes its appearance.

Request body

Response: { "ok": true }

PUT /api/admin/workspaces/:workspaceId/members

Replaces the workspace’s member list wholesale — this is a set, not a diff. Fails with 409 CONFLICT on a Personal workspace, which can’t take more than its one member.

Request body

Response: { "ok": true }

DELETE /api/admin/workspaces/:workspaceId

Deletes the workspace and, by cascade, every log, tag, task, and attachment in it, plus its files under the storage backend’s workspaces/<slug>/ prefix.

Response: { "ok": true }

Instance Settings

A flat key-value store (settings table, both keys and values are strings) for instance-wide configuration. GET/PUT accept and return whatever keys are there — the API doesn’t enforce a fixed shape.

GET /api/admin/instance

Response: { "settings": { "defaultPageSize": "10", "maxAttachmentSize": "10485760", "allowedFileTypes": "image/png,image/jpeg,...", "storageBackend": "local", "mirrorPath": "" } }

PUT /api/admin/instance

Upserts settings — keys not included in the body are left untouched.

Request body: any { "key": "value" } object (all values must be strings). The settings page in the UI writes these keys:

Response: { "ok": true }