feature: optional per-query required_permission, on top of sharing #4

Merged

Gilles merged 1 commit from feature/3-required-permission into master

2026-10-26 08:37:21 +00:00

Gilles commented

2026-10-26 08:24:15 +00:00

Owner

SavedQuery.required_permission (blank by default) names an extra Django permission a viewer must additionally hold to see a specific query's results, on top of the existing owner/shared_users/shared_groups scoping. Only gates results (can_view_results), never the query's own definition visibility.

Motivated by argus/backend#17 (homepage overview dashboard), to allow reserving a specific aggregate's data to a finer right than plain group membership when needed.

Closes #3.

🤖 Generated with Claude Code

https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh

`SavedQuery.required_permission` (blank by default) names an extra Django permission a viewer must additionally hold to see a specific query's results, on top of the existing owner/shared_users/shared_groups scoping. Only gates results (`can_view_results`), never the query's own definition visibility. Motivated by argus/backend#17 (homepage overview dashboard), to allow reserving a specific aggregate's data to a finer right than plain group membership when needed. Closes #3. --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh

Gilles added 1 commit

2026-10-26 08:24:15 +00:00

feature: optional per-query required_permission, on top of sharing

ci / test (3.11) (pull_request) Successful in 31s

Details

ci / test (3.15) (pull_request) Successful in 36s

Details

ci / lint (pull_request) Successful in 59s

Details

ci / publish (pull_request) Has been skipped

Details

ci / test (3.12) (pull_request) Successful in 35s

Details

ci / test (3.13) (pull_request) Successful in 33s

Details

ci / test (3.14) (pull_request) Successful in 34s

Details

63f1c3ab2a

SavedQuery.required_permission (blank by default) names an extra
Django permission a viewer must additionally hold to see that
specific query's results -- checked in can_view_results, never
replacing the usual view_savedquery_results + shared_with rules, and
never affecting the definition's own visibility (can_view_savedquery).
Lets a host app reserve one query's data within an otherwise shared
dashboard to whoever also holds some more specific permission.

Settable via the existing create/update API, like any other field.

Closes #3.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh