Skip to main content
The Dashboard tab uses the same stable block engine as the homepage, but exposes blocks designed for signed-in customer data.

​
Starting presets

Applying a preset replaces the block arrangement in the form. It is not permanent until you select Save Changes.

​
Dashboard blocks

​
Width and duplication

Dashboard blocks can use full or half width. Adjacent half-width blocks form a row at wide viewports and stack on smaller screens. Duplicate a data block when you need two views with different titles or limits.
The service, invoice, and ticket limits are applied by the dashboard block data layer. They are not the same as Paymenter’s global pagination setting.

​
Alerts behavior

Alerts can derive notices from unpaid invoices, services approaching expiry, and missing two-factor authentication. A manually configured announcement supports Markdown and one of four tones: Info, Success, Warning, or Critical. Daily tips rotate from the configured list.

​
Monthly cost overview

The Monthly Cost Overview estimates a monthly recurring amount from active paid services, normalizing daily, weekly, monthly, and yearly billing cycles. It separately shows pending invoice balances due through the end of the current month and paid invoices due within the month. Free and one-time plans are excluded from the recurring estimate. Each currency is rendered independently. LucentUI never combines unlike currencies into a misleading total, and the visitor’s selected currency is shown first. The radial variant emphasizes invoice payment progress; the bars variant provides a denser comparison. Credit figures are obscured by default. The eye button changes only the reveal state; it does not open the Credits page. Selecting any other part of the credit card still navigates to the account credit screen. This behavior is consistent across Cards, Strip, and Minimal stat variants.

​
Performance

The dashboard is rendered server-side from cached settings and bounded data queries. Blocks should remain focused: increasing every limit or cloning many live-data blocks can increase database work and reduce scanability.
When the Greeting Card uses Stat Strip, disable a separate Stat Cards block unless repeating the same figures is intentional.
Last modified on September 10, 2026