Web Health Status - Custom Site Owner Dashboard and Client Control Panel

You look after a Drupal site, or run one for a client, and every morning the same question comes back: is everything fine, and what happened yesterday? Answering it means a tour through Reports, People, orders, form results and the ticket tool. Web Health Status gathers those answers on one screen, /admin/web-health-status, written for the person who owns the site.

The day you install it, a Home entry appears in the administration menu and the dashboard assembles itself from what the site already has: who is on the site right now, accounts created this month, the admin pages you open most, whether core and modules are up to date. Install Commerce or Webform and the sales and leads blocks join in.

What you get

• Activity at a glance. Visitors right now and over the last 7, 30 and 365 days, anonymous and logged-in apart, refreshed every 30 seconds while the page is open.
• Quick actions ranked by real use. Shortcuts discovered from the administration menu and sorted by how often you click them; reorder, hide, pick an icon or add your own.
• Sales, Top products, Leads, Registrations. Revenue by period and best sellers from Drupal Commerce; one block per Webform; new accounts when self-registration is allowed.
• Suggestions. A twelve-point checklist in four groups (search ranking, conversion, visibility, trust and compliance) you tick off or skip.
• Site health. Outdated modules, core version and security status from the core Update module; a modal turns the list into a valuation task when AI Ticket Chat is installed.
• Support tasks and team. With AI Ticket Chat: tasks waiting for your reply, six status boxes per department, who is working now, and a Support team page with Performance, Team, Backlog, Work queue, Holidays and Absences tabs.
• Edit view. One click turns every block into a card you drag, resize to a third, half or full width, or hide; the layout is shared by everyone who opens the dashboard.
• Notifications and roles. Ten notification types ring the suite bell, from a security update to an activity spike; a role and block matrix, one view permission per block, a login redirect and a Logs tab.

How it works

Each of the fourteen blocks asks the site what it can show: Commerce present, Sales renders; Webform present, one Leads block per form; a suite module absent, its block moves to a pinned section with a link to install it. Everything is counted from local tables and cached briefly; cron sends the notifications, re-imports the bundled Spanish translation and runs the provider reports below. Administrators configure it at Administration » Home » Settings (/admin/web-health-status/ajustes). Block order, widths and hidden blocks live in State, site-wide.

Free, and what the optional service adds

Everything above works with Drupal, this module and the Central Connect AI SDK, with the site connected to nothing: every block, the layout editor, the matrices, the notifications, the login redirect and the Logs tab.

The Support services block and a few premium touches need a service provider. The reference provider is Suscripciones Tangram, operated by Tangram Consulting; its address is the default in the SDK settings form, and any provider exposing the same API can take its place. You connect the site there explicitly. A connected provider adds the catalogue of support services with each one's state on your site, a checkout, trial and monthly-to-yearly upgrade flow that hands over to Stripe on the provider's side, an AI balance card with recharge and billing portal, a login to the provider's client panel, and four AI-written growth suggestions a month when that service is active. The Sales tracking and Multi-role assistant blocks show their premium state from the same catalogue; the provider can pull the health snapshot with a per-site token, and cron reports support minutes when a support contract exists.

Before you connect, no data about your site goes anywhere; the only outbound request is a read of the provider's public catalogue, so the block can show what exists. A feature you have not contracted shows a plain button pointing to its service card, never a broken screen. The provider is a separate service, outside Drupal's security advisory coverage.

Use cases

• An agency hands a finished site to its client with a Home page the client understands.
• A shop owner opens one screen every morning: sales today, top products this week, leads from the contact form, pending updates.
• A support team on AI Ticket Chat sees who is working and what is waiting, and plans holidays and the backlog.

Getting started

1. composer require drupal/web_health_status and enable the module; the Central Connect AI SDK comes with it.
2. Grant view tangram owner dashboard, edit tangram owner dashboard or administer tangram owner dashboard to the right roles; each block also has its own view permission.
3. Open Administration » Home (/admin/web-health-status).
4. In Administration » Home » Settings (/admin/web-health-status/ajustes) tick the role matrices and the roles that land on the dashboard after login.
5. Click Edit view and arrange the blocks. Optionally, connect a provider in the SDK settings form and grant activate tangram support services to whoever may contract services.

Requirements

• Drupal 11.1 or newer, and the PHP version it requires (8.3); core user and system, plus Update, Database Logging and Locale for the health tiles, the Logs tab and the translation.
• Central Connect AI SDK, required: header, icons, modals, bell and the provider connection.
• Optional: Commerce, Webform, AI Ticket Chat, Multi-Role AI Chatbot, Sales Pipeline AI, Redirect After Login; for the paid features, a provider exposing the Suscripciones Tangram API.

Privacy and security

• Sessions, users, orders and submissions are counted, never copied. Two tables hold the discovered shortcuts with their click counters and the ideas sent from the feedback modal.
• Layout, checklist progress and discarded services live in State and never enter exported configuration.
• Every state-changing endpoint is a POST behind the CSRF request header token and its own permission; the dashboard is never anonymous.
• Health tiles are visible to the roles granted the Web health block. The same snapshot is served on /api/tangram/health-report only to a caller presenting the per-site pull token provisioned through the SDK, compared in constant time and flood-limited.
• Outbound calls: the public catalogue read on render; once connected, the authenticated catalogue, the suggestions poll and support-minutes report from cron, the feedback you send, and the checkout, upgrade, recharge, portal and panel-login requests you trigger. The checkout sends the operator's e-mail address and the chosen plan to the provider, which redirects to Stripe; creating a provider account sends e-mail, name and password.

Part of the Central Connect AI suite

The suite is a set of free GPL modules sharing one header, one bell and one optional provider connection; Web Health Status is its front door. Central Connect AI SDK is the required foundation. AI Ticket Chat feeds the support blocks and the Support team page and receives the valuation tasks. Multi-Role AI Chatbot and Sales Pipeline AI each get a summary block linking to their own screens.

Similar projects and how this one differs

• Dashboard builds per-role dashboards from any block with Layout Builder; Web Health Status ships fixed business blocks that appear on their own.
• Drupal Remote Dashboard monitors many sites from one console; this module is the panel inside one site and only exposes a token-protected snapshot for a connected provider to pull.
• Warden reports core and module versions to a central server with no owner-facing screen; here the screen comes first and the report endpoint is secondary.
• Monitoring is a sensor framework for operators and tools such as Nagios; it has no sales, leads or support blocks.
• Commerce Reporting is full sales reporting for Drupal Commerce; this module shows four totals and the top products and leaves the detail to it.

Development

Parts of this module were written with the assistance of AI-based coding tools, as required by the policy on the use of AI when contributing to Drupal. All the code has been read, corrected, tested and is maintained by the human maintainer listed below, who takes full responsibility for it.

Maintainers and sponsor

Maintained by pedroromán. Sponsored by Tangram Consulting. Issues, ideas and contributions are welcome in the issue queue.