The project's home page is a widget dashboard you arrange yourself. The default set covers what most projects look at first; Add widget offers the rest, and each widget's menu configures or removes it. The layout is saved per project, for everyone.
Widget kinds#
| Widget | Shows |
|---|---|
| Tile | One number — orders this week, revenue, documents in a collection, open form records — with a delta against the previous period. |
| Chart | A time series of the same metrics. |
| Ready orders | Orders waiting to be shipped, with one-click status changes. |
| Recent orders | The last orders placed. |
| Form records | The newest submissions of a chosen form. |
| Analytics tile / chart | Google Analytics metrics once Statistics is connected. |
| Traffic tile / chart, Top pages | The platform's own traffic numbers — no setup needed (see Traffic). |
| Visits / Visits chart | This month's visits, and the current period against the previous one. |
The Visits, Visits chart and Top pages widgets carry a Platform / GA4 switch. Once Google Analytics is connected in Statistics, they open on GA4; a project without it shows the platform's own numbers. The default dashboard of a connected project also shows the GA4 page-views tile instead of the platform views tile — until you customize it, after which your own layout is what counts. | Storage | The space the project's files take. | | AI credits | The wallet the AI assistant spends. | | Assistant | What is left to finish on the site — missing SEO descriptions, favicon, share image, article images. The assistant runs the same check, so asking it "what is missing?" gives the same list, and it can fill the missing descriptions in one go. | | Activity | The latest entries of the activity log. | | Module widget | A widget an installed module declares. |
What the shop numbers count#
Over the chosen period (7, 30 or 90 days, by the day an order was placed):
- Orders and Top products count orders that were actually placed — in progress or completed. Carts, refused orders and closed ones (cancelled, or never paid) are left out.
- Revenue is the total of completed orders only, shown in the currency of the project's home country (the country of its first language).
- Finished invoices counts the invoices issued in the period.
Widget data loads lazily and is shared between widgets, so a dashboard full of tiles costs one read per source.
Managers also see the plan card above the widgets — the current tier and its weekly credits. When the platform team has set a required plan the card is highlighted with the plan and the date to subscribe by, and its link leads straight to the shop.
From an agent or the API#
The widget list can also be set by an AI agent in the project's workspace (the MCP tools readConsoleSettings → writeConsoleOverview) or by the API (POST /api/project/console/overview, the SDK's project.console.overview(widgets, days)). The write replaces the whole dashboard and is checked against the widget kinds this console knows. Like the console's own setting it is one for both environments, and each write appears in Activity with the source API token. Writing needs the owner role, or a project token with the console grant (see Pinned menu); a manager's personal access token carries the owner role in that project.
Who sees it#
Every member. Widgets that read a capability the member does not have render empty rather than failing.