Skip to content

Database governance built for humans and agents — controlling changes and access across every major database.

docs: workspace admin roles carry all four saved-query permissions (codex review)

Danny64d49c4831f8
diff --git a/docs/design/saved-queries-model.md b/docs/design/saved-queries-model.md
index cdec15826b..fcd62d8fbc 100644
--- a/docs/design/saved-queries-model.md
+++ b/docs/design/saved-queries-model.md
@@ -265,7 +265,9 @@ carry `create` and `search`; the automation roles (`projectReleaser`,
saved-query surface entirely — which is what makes the share-with-project
snapshot's role filter meaningful for them. `projectOwner` carries
project-scoped `list` + `manage`; `workspaceAdmin`/`workspaceDBA` carry
-them workspace-scoped. `manage` implies the Search gate — Search evaluates
+**all four** workspace-scoped — they are human operator roles, and an
+admin who could manage everyone's queries yet not draft their own (or
+list their own folders, `search`-gated) would be absurd. `manage` implies the Search gate — Search evaluates
`discover ∨ admin` in the handler — so a manage-only custom role can
still enumerate what it manages; there is no hidden permission
coupling.