Skip to content

docs: teams / orgs / collaboration implementation plan#5

Merged
PolGuixe merged 1 commit into
mainfrom
docs/teams-orgs-plan
Jun 5, 2026
Merged

docs: teams / orgs / collaboration implementation plan#5
PolGuixe merged 1 commit into
mainfrom
docs/teams-orgs-plan

Conversation

@PolGuixe
Copy link
Copy Markdown
Member

@PolGuixe PolGuixe commented Jun 5, 2026

Adds docs/TEAMS_AND_ORGS_PLAN.md — a full implementation plan for multi-tenant
collaboration, plus a README link.

Locked scope

  • Shared access + pessimistic document locking (no real-time CRDT)
  • Organization → Team → resources (two-level tenancy)
  • Granular RBAC (permission catalogue)
  • Keep Supabase Auth (ADR-1) — adapt cpatpa/PIP's data model, not its auth stack

What the doc covers

Notes

  • Docs only — no runtime/CI/config changes.
  • Phase 0 (RLS + uuid migration) is a standalone security win and can ship first.
  • §13 lists open questions for sign-off before Phase 1.

🤖 Generated with Claude Code

Comprehensive design doc for multi-tenant organizations, teams, granular
RBAC, shared access with pessimistic document locking, and the RLS
foundation (also closes the upstream-willchen96#144 security gap).

Grounded in Mike's current schema and the cpatpa/PIP reference fork
(adapted to keep Supabase Auth per ADR-1). Includes target data model,
RLS strategy, backend/frontend surface, zero-loss migration/backfill,
an 8-phase delivery plan (~9-12 wk solo / 5-7 wk for two), risks, and a
testing strategy centered on tenant isolation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@PolGuixe PolGuixe merged commit bbb3ee8 into main Jun 5, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant