InfoThis screen is Builder → Database in the sidebar. The in-product Setup Guide refers to the same screen as Data Model, and older documentation calls it the model builder or ER editor. All four name the ER canvas documented here.
The next important feature of the admin panel is the ER editor. It allows you to check your ER model, define queries, handle workflows, and a lot more. It is the backbone to handle the data side of your database infrastructure:
The CYPEX administration panel gives operators a single place to administer and manage CYPEX as a whole. v2.0.0 reorganizes it around how operators actually set up and run a multi-tenant deployment. This section is the navigation map for that information architecture: each entry below links to a topic-scoped page documenting the corresponding admin screen.
The table below is the authoritative list of sidebar labels and who sees each one. Labels are the strings the product renders — use them verbatim in procedures.
A single CYPEX deployment can handle a large set of applications running inside the same database. Open Builder → Applications in the sidebar and CYPEX presents a list of every app currently deployed on the system.
You can easily manage your applications from this menu. This includes but isn’t limited to:
Let’s walk through this important page:
A workflow in CYPEX is a state machine stored with your data model: named states, allowed transitions, and which roles may fire each transition. Once you enable enforcement, it is applied in the database — a CHECK constraint on the state column plus a trigger that rejects any transition you did not model, and checks the caller’s role against the transition’s permissions. The UI only offers what the database would accept anyway.
