v2.0.0 replaces the single long-lived JWT with an access token / refresh token pair. This page explains the model, the settings that govern it, and the two configuration mistakes that break a deployment.
Under the old model a token was minted at login and stayed valid for its whole lifetime. Deactivating a user or changing their role did nothing until that token expired — potentially days later.
Platform Admin → Database Migrations is the in-app runner for CYPEX’s own
framework schema migrations — the changes CYPEX applies to its internal
cypex schema when the platform is upgraded.
This screen is System Administrator only (system admin visibility).
InfoThis is not where you migrate your data model. Changes to your own tables are made in Database.
The in-app runner applies migrations. It does not tell you whether it is safe to apply them, what they change, or how to verify the result — that is what the upgrade documentation is for. For v2.0.0 specifically, run the upgrade from Upgrade to v2.0.0 and treat this screen as one step inside that procedure, not a substitute for it.
Under Platform Admin → Storage & Repositories, you define the Git repositories CYPEX uses to fetch extensions. Basically, you give CYPEX access to a Git repository which contains all of the extensions in a format accessible to CYPEX:
Repository Configuration
Configured repositories list their Title, User Name, Path, Branch, and a masked Personal Access Token. Actions let you test the connection, edit, or delete a repository.
The configuration is straightforward — add the Git data and test the connection. CYPEX is then fully connected and you can easily add extensions to the system as needed. Click + Add to open the form:
Platform Admin → Internal Schema Browser shows the internal cypex
schema — the platform’s own metadata tables, not your application data.
This screen is System Administrator only (system admin visibility) and is
intended for advanced debugging.
| Internal Schema Browser | Database | |
|---|---|---|
| Schema | cypex — platform metadata | Your application schemas |
| Contents | The tables CYPEX uses to store applications, modules, organizations, roles, and object definitions | The tables, views, and workflows you design |
| Purpose | Inspecting platform state while debugging | Building the data model your applications render |
Warning
To install SQL fragments you can use the Extensions entry. Click the action button to easily deploy extensions.
There are countless extensions inside the default repository which can be used:
By default, the CYBERTEC repository for CYPEX is enabled. However, you can easily add more repositories as needed. For more information, see the section on Storage Repositories.
