Skip to content

[GrantFox][High] Centralize tenant authorization checks #1146

Description

@greatest0fallt1me

Summary

Centralize tenant authorization checks

Why this matters

A missed tenant predicate can expose another tenant’s records.

Scope

Create reusable authorization helpers and an audited route-to-policy matrix for all sensitive reads and writes.

Acceptance criteria

  • Every tenant-scoped route requires tenant context.
  • Cross-tenant identifiers cannot reveal existence or data.
  • Privileged bypasses are explicit and audited.
  • Negative tests cover every sensitive route family.

Validation

Add regression coverage for existing behavior, failure modes, authorization boundaries, and compatibility. The implementation must pass the repository CI checks.

Non-goals

  • Typo-only, formatting-only, or documentation-only changes.
  • Unrelated refactors or dependency upgrades.
  • Weakening existing security, authorization, CI, or production safeguards.

Contributor application

Before implementation, comment with relevant experience, a 1–4 bullet approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding.

PR requirements

Use a feature branch, include Closes #<issue-number>, check every acceptance criterion, link criteria to code/tests, explain security and failure-mode considerations, and pass CI.

Reward-readiness

This is a substantive GrantFox campaign issue. Merge and CI success do not by themselves guarantee reward eligibility; final reward-readiness is determined by campaign review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions