928f5abe3f
Before this change, the `organization_members` table keyed on user_id — joining an org as a Viewer in tenant T meant only that one user got visibility on shared KBs/agents, while the rest of T (including its Owner) saw nothing. The mismatch surfaced as confusing UX bugs: "my colleague shared this with us, why can't I see it?" This change replaces `organization_members` with `organization_tenant_members`. Membership and Org-RBAC role now key on (org_id, tenant_id); `representative_user_id` stays as a display-only label of the user who first brought the tenant in. Permission resolution gains a 3-D cap so tenant-RBAC stays honest under cross-tenant sharing: effective = min(share.Permission, tenant_org_role, tenant_role_cap) where tenant_role_cap pins tenant Viewers to OrgRoleViewer regardless of the org-level grant. A Viewer in their own tenant cannot edit a shared KB even if the org granted Editor — preserves the "Viewer = read-only everywhere" promise. Migration 000045 backfills `organization_tenant_members` from the old table by collapsing each (org, tenant) group to its max role, then renames the old table to `organization_members_pre_plan3` for safe rollback. Sqlite mirror (Lite mode) is fresh-bootstrap: the init schema replaces the old table directly. Routes: member-management URLs change from `:user_id` to `:tenant_id`. Org create / join / leave now require Admin+ in the caller's tenant — joining an Org affects everyone in T, so the decision can't sit with a Viewer. Frontend: OrganizationSettingsModal + store update to address members by tenant_id.
28 lines
1.4 KiB
SQL
28 lines
1.4 KiB
SQL
-- Reverse migration for 000045_org_tenant_members.
|
|
--
|
|
-- Restore organization_members from the parked _pre_plan3 table and drop
|
|
-- the new tenant-scoped table. Because we only RENAMEd the original on
|
|
-- the way up, no data is lost on rollback — the legacy rows are still
|
|
-- intact under the renamed table.
|
|
--
|
|
-- If the parked table no longer exists (e.g. a later destructive
|
|
-- migration already dropped it), this script falls through gracefully:
|
|
-- the IF EXISTS guards leave the database in whatever state it was in.
|
|
|
|
DO $$ BEGIN RAISE NOTICE '[Migration 000045] Reverting Plan 3'; END $$;
|
|
|
|
-- Move legacy table back into place.
|
|
ALTER TABLE IF EXISTS organization_members_pre_plan3 RENAME TO organization_members;
|
|
|
|
-- Restore index names so the application code can find them by their
|
|
-- documented identifiers.
|
|
ALTER INDEX IF EXISTS idx_org_members_org_user_pre_plan3 RENAME TO idx_org_members_org_user;
|
|
ALTER INDEX IF EXISTS idx_org_members_user_id_pre_plan3 RENAME TO idx_org_members_user_id;
|
|
ALTER INDEX IF EXISTS idx_org_members_tenant_id_pre_plan3 RENAME TO idx_org_members_tenant_id;
|
|
ALTER INDEX IF EXISTS idx_org_members_role_pre_plan3 RENAME TO idx_org_members_role;
|
|
|
|
-- Drop the new table. The unique/secondary indexes go with it.
|
|
DROP TABLE IF EXISTS organization_tenant_members;
|
|
|
|
DO $$ BEGIN RAISE NOTICE '[Migration 000045] Plan 3 reverted'; END $$;
|