Release Notes v2.0.0
v2.0.0 is the release in which CYPEX becomes a multi-tenant PostgreSQL application platform. Tenancy is a first-class object (Organizations), isolation is enforced in the database (Row-Level Security), authorization is two-dimensional (Capabilities × Data Scope), schema exposure is explicit (Schema Access), identity can be federated (SSO Gateway), and outbound integrations are governed (allowlist, credentials, enablement, audit).
WarningThis is not a drop-in patch. v2.0.0 changes the permission and tenancy model. Read the Upgrade to v2.0.0 operator guide before planning a maintenance window, then the Upgrading to v2.0.0 technical reference for the database detail.
| Area | What changed |
|---|---|
| Organizations | Multiple tenants in one deployment, isolated by PostgreSQL RLS on 37 tables |
| Roles | Three role types; Capabilities and Data Scope configured as separate concerns |
| Schema Access | Per-organization control over which database schemas (modules) are available |
| Admin panel | New information architecture, role-aware navigation, Setup Guide, Access Preview |
| SSO | Dedicated SSO Gateway service, five provider types, pending-approval gate; LDAP and local login unchanged |
| Connectors | Allowlist, encrypted credentials, connector builder, two-level enablement, execution audit |
| Breaking changes | RLS, role semantics, Schema Access, new service, route changes |
A CYPEX deployment can serve more than one tenant — an Organization — from the same PostgreSQL database. Isolation is enforced by Row-Level Security in the database, not by UI filtering.