v2.0.0 Migration Reference

CYPEX v2.0.0 introduces multi-tenant Organizations with PostgreSQL Row-Level Security (RLS). Tenant isolation is enforced in the database, not by application-layer filters that can be bypassed or misconfigured. This is the most significant schema and permission-model change since v1.0.0.

This section is the canonical place to plan, validate, and execute a v2.0.0 upgrade. It is written from the perspective of factual upgrade behavior: what the migrations actually do, what is additive, what is breaking, and what is behavior-changing.

• CYPEX operators planning a production upgrade.
• DBAs reviewing schema, RLS, and role changes.
• Tech leads evaluating whether and when to upgrade.

If you are only looking for the detailed procedure to set up multiple organizations after the upgrade, jump straight to Detailed organization setup.

Info

Haven’t started the upgrade yet? Read the Upgrade to v2.0.0 operator guide first — it covers every breaking change across Organizations, SSO, and Connectors in one walkthrough. This section is the deeper technical reference for the Organizations/RLS portion of that guide.

In one sentence: CYPEX moves from a single-tenant model to a multi-tenant model where every tenant is an Organization, isolated by PostgreSQL RLS.

The full classification is:

• Breaking changes — permission changes that affect existing users and integrations.
• Behavior changes — defaults that change how the platform behaves without breaking existing integrations.
• Additive changes — new tables, functions, indexes, and roles that do not affect existing behavior.

1. Conceptual overview — understand the new model.
2. Upgrade test matrix — see what was verified, and confirm your scenario is covered.
3. Pre-upgrade checklist — confirm your environment is ready.
4. RLS impact on existing data — the answer to the most common question.
5. Roles and permissions — understand the new role model.
6. Default password policy — understand the new defaults.
7. Rollback constraints — know what you can and cannot undo.

• Detailed organization setup — assign clients to organizations after the upgrade.

• Upgrade to v2.0.0 — the mandatory operator entry point this reference supports.
• v2.0.0 release notes — the release entry that introduces multi-tenancy.