ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
e5ad9b6cf8
TenantAtlas/.specify
History
ahmido d90fb0f963 065-tenant-rbac-v1 (#79) 
PR Body
Implements Spec 065 “Tenant RBAC v1” with capabilities-first RBAC, tenant membership scoping (Option 3), and consistent Filament action semantics.

Key decisions / rules

Tenancy Option 3: tenant switching is tenantless (ChooseTenant), tenant-scoped routes stay scoped, non-members get 404 (not 403).
RBAC model: canonical capability registry + role→capability map + Gates for each capability (no role-string checks in UI logic).
UX policy: for tenant members lacking permission → actions are visible but disabled + tooltip (avoid click→403).
Security still enforced server-side.
What’s included

Capabilities foundation:
Central capability registry (Capabilities::*)
Role→capability mapping (RoleCapabilityMap)
Gate registration + resolver/manager updates to support tenant-scoped authorization
Filament enforcement hardening across the app:
Tenant registration & tenant CRUD properly gated
Backup/restore/policy flows aligned to “visible-but-disabled” where applicable
Provider operations (health check / inventory sync / compliance snapshot) guarded and normalized
Directory groups + inventory sync start surfaces normalized
Policy version maintenance actions (archive/restore/prune/force delete) gated
SpecKit artifacts for 065:
spec.md, plan/tasks updates, checklists, enforcement hitlist
Security guarantees

Non-member → 404 via tenant scoping/membership guards.
Member without capability → 403 on execution, even if UI is disabled.
No destructive actions execute without proper authorization checks.
Tests

Adds/updates Pest coverage for:
Tenant scoping & membership denial behavior
Role matrix expectations (owner/manager/operator/readonly)
Filament surface checks (visible/disabled actions, no side effects)
Provider/Inventory/Groups run-start authorization
Verified locally with targeted vendor/bin/sail artisan test --compact …
Deployment / ops notes

No new services required.
Safe change: behavior is authorization + UI semantics; no breaking route changes intended.

Co-authored-by: Ahmed Darrazi <ahmeddarrazi@MacBookPro.fritz.box>
Reviewed-on: #79
2026-01-28 21:09:47 +00:00
..
memory 065-tenant-rbac-v1 (#79) 2026-01-28 21:09:47 +00:00
scripts/bash dev-merges/c709b36 (#3) 2025-12-21 23:15:12 +00:00
templates docs: enforce RBAC constitution gates in spec templates (#78) 2026-01-27 22:09:56 +00:00
plan.md docs: deprecate .specify specs and update references (#53) 2026-01-10 21:40:46 +00:00
README.md docs: deprecate .specify specs and update references (#53) 2026-01-10 21:40:46 +00:00
research_t186.md docs: deprecate .specify specs and update references (#53) 2026-01-10 21:40:46 +00:00
spec.md docs: deprecate .specify specs and update references (#53) 2026-01-10 21:40:46 +00:00
tasks.md docs: deprecate .specify specs and update references (#53) 2026-01-10 21:40:46 +00:00

README.md

.specify/ (Tooling)

This folder contains SpecKit tooling (templates, scripts, constitution, etc.).

Important

  • Do not create new feature specs in .specify/spec.md, .specify/plan.md, .specify/tasks.md.
  • Active feature specs live under specs/<NNN>-<slug>/:
    • spec.md
    • plan.md
    • tasks.md
    • checklists/requirements.md

The files .specify/spec.md, .specify/plan.md, .specify/tasks.md may exist as legacy references only.