InfoLooking for the conceptual reference (“what is an Organization?”)? See Organizations.
After the v2.0.0 upgrade, every CYPEX deployment starts with a single Default Organization that holds all existing data. This page is the entry point for setting up additional organizations and assigning existing clients / schemas to them.
- You want to split a single-tenant deployment into multiple organizations (one per client, per business unit, or per environment).
- You need to backfill the
organization_idcolumn on existing application-schema tables. - You are operating the cutover from “everything on Default Organization” to “each row tagged with the right organization.”
- Prepare the existing database — pre-flight checks, downtime planning, smoke-test environment.
- Enable RLS — the SQL primitives for enabling and configuring RLS on application-schema tables.
- Assign clients to organizations — uses the client-add-organization-id SQL template.
- Verify and roll back — verification queries and the rollback procedure if something goes wrong.
- Upgrading to v2.0.0 — for the upgrade-time procedure.
- RLS impact on existing data — for the visibility guarantees before you start.
- Roles and permissions — for the role model you are operating within.
- client-add-organization-id-template.sql
— SQL template for adding
organization_idto client application-schema tables. See Assign clients to organizations for how to customize and run it. This migration has failed in the field. Read Failure modes before production rollout.