Database governance built for humans and agents — controlling changes and access across every major database.
Go cicddata-governancedata-maskingdata-securitydatabase-accessdatabase-governancedevopsdevsecopsflywaygitopsliquibasemongodbmysqloraclepostgresqlschema-migrationssecuritysql-clientsqlservertidb
docs: share-with-project skips allUsers; policy accepts only user and group (codex review)
Danny7aeb9a95b4b5
diff --git a/docs/design/saved-queries-model.md b/docs/design/saved-queries-model.mdindex a3035c9e37..4bd61b32c8 100644--- a/docs/design/saved-queries-model.md+++ b/docs/design/saved-queries-model.md@@ -318,7 +318,13 @@ its `group:` and `user:` bindings, not an expansion of members — into thepolicy at the chosen level. Only bindings **whose role carries`bb.savedQueries.search`** are included: a role deliberately kept off thesaved-query surface (a CI releaser, say) must not be swept into content-grants that outlive its project role. Snapshots keep group dynamism (a group+grants that outlive its project role. `allUsers` members — which+self-hosted project IAM permits — are **skipped, never expanded**: the+per-object policy accepts only `user:` and `group:` principals+(`SetIamPolicy` rejects anything else), and freezing a workspace-wide+audience into per-user grants would be exactly the member explosion the+snapshot avoids. The dialog surfaces the skip so the sharer can grant a+group instead. Snapshots keep group dynamism (a groupgaining a member propagates, since the entry stores the group reference) butnot membership dynamism (a principal added to the project later is re-sharedby the owner, as in every group-based peer). Project bindings carrying a CEL