# UX-009 Certification: Cross-Project and Tenant Boundaries

Date: 2026-02-22  
Checklist Item: `UX-009`  
Ticket: `ISIS-0234`

## Journey Scope

User state: authenticated user/operator in scoped Isis environment  
Journey: sign in with scoped tenant/project context -> execute user journeys
across jobs/workflows/outputs -> backend enforces project scope and rejects
mismatches  
Coverage target: project/tenant context is captured in UI, propagated on API
calls, and enforced by services

## Evidence Matrix

| Requirement                                                      | Evidence                                                                                                                                                                                                              | Status |
| ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ |
| UI captures project scope at sign-in                             | `apps/isis/web/src/pages/LoginPage.tsx` now includes `Project ID (optional)` input and passes `tenant.projectId` into `login(...)`.                                                                                   | Pass   |
| Web client propagates project scope on all API requests          | `apps/isis/web/src/api/IsisClientProvider.tsx` now adds `X-Isis-Project-Id` to shared client headers and recomputes client config when project scope changes.                                                         | Pass   |
| Header propagation is test-covered                               | `apps/isis/web/src/api/IsisClientProvider.spec.tsx` verifies all tenant headers include project scope when present and verifies project header removal when scope is absent.                                          | Pass   |
| Auth recovery journey preserves scoped project boundary context  | `apps/isis/web/src/App.e2e.spec.tsx` anonymous-recovery test now signs in with project scope and asserts `login(...)` receives `tenant.projectId`.                                                                    | Pass   |
| Project scope derives correctly from auth claims/session context | `apps/isis/web/src/auth/rbac.spec.ts` and `apps/isis/web/src/auth/AuthContext.spec.tsx` verify `projectId` extraction/derivation from JWT claims into effective session tenant context.                               | Pass   |
| Backend rejects cross-project scope mismatches                   | `apps/isis/generation-api/src/app.auth.spec.ts`, `apps/isis/workflow-registry/src/app.auth.spec.ts`, and `apps/isis/output-registry/src/app.auth.spec.ts` all validate 403 behavior for project scope mismatch cases. | Pass   |

## Reproduction Commands

```bash
pnpm --filter @isis/web exec vitest run src/api/IsisClientProvider.spec.tsx src/App.e2e.spec.tsx src/auth/rbac.spec.ts src/auth/AuthContext.spec.tsx
pnpm --filter @isis/generation-api exec vitest run src/app.auth.spec.ts
pnpm --filter @isis/workflow-registry exec vitest run src/app.auth.spec.ts
pnpm --filter @isis/output-registry exec vitest run src/app.auth.spec.ts
```
