ahmido 2ca989c00f feat/031-tenant-portfolio-context-switch (#32 )

Tenant Switch implemented

Co-authored-by: Ahmed Darrazi <ahmeddarrazi@adsmac.local>
Reviewed-on: #32

2026-01-04 21:28:08 +00:00

Plan: Tenant Portfolio & Context Switch (031)

Branch: feat/031-tenant-portfolio-context-switch
Date: 2026-01-04
Input: spec.md

Approach

Decide on the tenant context mechanism:
- Preferred: Filament tenancy (tenant in URL) + built-in tenant switcher.
- Fallback: session-based Current Tenant + visible banner (avoid global/DB state as “source of truth”).
Add data model pieces:
- tenant membership/role mapping
- tenant environment attribute
- optional user preferences (favorites + last used)
Implement a single TenantContext resolver (HTTP + console) and central authorization gate/policy:
- deny-by-default if no access
- keep INTUNE_TENANT_ID as console override for automation
Update tenant-scoped resources/services to use TenantContext instead of Tenant::current() and ensure base queries are tenant-scoped.
Extend TenantResource into a portfolio view:
- access-scoped query
- environment/health columns
- “Open” action + “Sync” action
- bulk “Sync selected”
Add restore guardrails:
- target tenant badge/header on restore pages
- type-to-confirm includes tenant/environment (e.g. RESTORE PROD)
Add targeted Pest tests for authorization, context switching, and bulk sync.
Run Pint + targeted tests; document rollout/migration notes.

Avoid a global tenants.is_current UI context (unsafe for MSP); prefer per-user context.
Avoid storing Current Tenant in the users table as the source of truth (cross-tab risk); prefer route/session context, optionally persisting “last used” separately.
Start with user-based tenant memberships; extend to organization/group principals later if needed.
Prefer deriving portfolio stats via relationships (withCount, withMax) initially; add denormalized summary columns only if needed for performance.