Files
qbit-sql-workbench/docs
james.maesandClaude Opus 5.5 ebef56f34b fix(security): guard the qbit's tables with a separate admin permission
The five tables used the same HAS_ACCESS_PERMISSION base (sqlWorkbench)
that every workbench user holds, so any user could read and write other
users' personal notebooks, cells, versions, pinned result snapshots and
the full execution audit through the generic /qqq/v1/table API.

- Tables now use adminPermissionBaseName (default sqlWorkbenchAdmin,
  validated to differ from the access base name).
- Cell, version and snapshot tables drop insert/update/delete
  capabilities, like the audit table.
- NotebookService and the history / snapshot audit lookups check the
  caller in code, then read and write as the system user (SystemUser,
  shared with ExecutionAuditor).
- Tests: a second ordinary user (and the owner) get permission denied
  from the table query executor on all five tables; the workbench API
  keeps working for ordinary users; admins can read everything.
- README / DESIGN document the admin permission.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 13:33:23 -05:00
..
2026-10-11 09:47:40 -05:00