Dashboard

The Dashboard is the first screen you see after logging into CYPEX. It gives you a high-level overview of what is happening inside your deployment: how many applications and users exist, a breakdown of active versus deactivated users, the in-product Setup Guide, and quick links in the sidebar to the most-used admin tasks.

From the dashboard you can jump directly into any section of the admin panel using the sidebar. The sections you see depend on your role and licence — see the sidebar reference.

New in v2.0.0, the dashboard carries a Setup Guide: a visual workflow that shows the correct order of operations for standing up a deployment and marks each step complete as you satisfy it.

Why it matters. In a multi-tenant platform the order is not arbitrary. The guide has you establish the tenant, define who may act in it, and open the org↔schema gate before modelling inside that boundary — then add users and generate applications. Schema Access decides whether a tenant can see a schema at all; without a grant, Model Builder stays empty for that organization no matter what roles exist. The guide encodes that order so you do not discover it by debugging an empty screen.

How it works. Progress is computed from real deployment state — whether organizations exist, whether roles exist, whether a schema and an organization both exist, whether the data model has tables, whether users exist, whether applications exist — not from a free-form checklist. Schema Access completes automatically as soon as a schema exists in the platform and an organization exists, which is normally already true the moment an organization is created, since org creation provisions that organization’s primary schema. No confirmation step is required on the Schema Access page itself. The guide is advisory: it never blocks you from using the rest of the admin panel while steps are still incomplete.

How to use it. The guide renders one of two paths depending on whether you are a System Administrator.

Info

Step 3 completes automatically, without any action on the Schema Access page itself. Creating an organization already provisions its primary schema, so as soon as an organization exists the platform also has a schema, and the step is satisfied. Opening Schema Access is only necessary if a tenant needs more than its primary schema, or if you want to verify grants — the guide does not track whether you visited the page.

Organizations and Schema Access are omitted from the shorter path because they are configured for that administrator by a System Administrator, not by them. Schema Access in particular is a System Administrator-only page. That is also why this path starts at roles: the tenancy boundary is already in place.

Tip

Steps 1–3 of the System Administrator path are where a first-time multi-tenant deployment usually goes wrong. An organization with no Schema Access grant sees nothing, no matter how its roles are configured. Use Access Preview after adding users to confirm a representative user can actually see what you expect, before you generate applications.

Info

The Setup Guide is the in-product workflow. The Setup guide page in these docs is the longer-form first-run walkthrough that also covers branding, SSO/LDAP, and repository configuration — topics the in-product guide does not track.

• Setup guide — first-run walkthrough for new admins.
• Administration panel — the full sidebar reference and visibility levels.
• Applications — the next stop once your data model and access boundary are ready.
• Database — the ER editor and query tooling behind every application.
• Access Preview — verify what a user can do and see before deployment.