Dashboard Reports
Spot pages that need attention when you open the dashboard.
- Version
- 1.1.9
- Released
- 10 November 2026
- Licence
- Commercial
Price £39.00
Check access and installationCheck your application before checkout
What it solves
The problem
Our site owners cannot easily spot stale or incomplete pages across the site.
What your site gets
Our team can review content health and publishing activity on the dashboard.
Questions buyers ask
- Which page issues can the dashboard highlight?
- Content health reports can show scheduled, expired, stale or incomplete page records.
- Can owners control the visible reports?
- Site owners can control which report widgets are visible.
- How can teams share report data?
- The package supports CSV export and scheduled digests.
Use it in your project
Review content health alongside publishing activity. Use the report to find expired, scheduled or incomplete pages and share the results with the team.
Picture it on your site
Before a release, use the reports to identify content that needs a decision: an expired page, an upcoming publication or incomplete information. Agree who acts on each finding and review the result after the change. Reporting is valuable when it leads to maintained content, not when the team simply collects another dashboard.
4 captures
Keep publishing work moving
- Show content-health and publishing-activity reports.
- Export report data or receive a scheduled digest.
Is this right for your project?
A publishing process people can follow
Start with the journey from a draft to a published page, not a list of status names. Who writes it, who checks it and who is responsible for the publication date? Choose the controls that match that journey. The benefit is a repeatable editorial process with fewer changes made outside the CMS; your team still supplies the content standards and the people who make publishing decisions.
Prove one complete release
Use a representative article or page to check editing, review, publication and the public result together. Include the site, language and related content that matter to your project. A scheduled record or approved status is only part of the result: visitors must see the right content at the right URL, and editors need to know how to correct it afterwards.
One customer organisation; up to 5 named users. Each entitlement covers one production website or application and up to two non-production environments, with a maximum of three active installations.
12 months of protected downloads, updates and included standard support.
You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy
Renewal is charged at the price current when you renew. The price is shown before you pay.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Paid checkout adds access to the purchasing account after payment. Review compatibility and site impact, then follow the installation steps for this package.
This listing has no page of its own in the demo. Open the demo to see Capell running.
Before you install
Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.
- Admin and public surfaces
- The package declares: administration screens. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- The manifest declares no package migrations. This does not establish that installation or runtime operations make no data changes. Uses package-local configuration and Capell metadata needed to enable the feature.
- Background work
- A complete jobs and scheduler assessment is not available here. Confirm background processing and worker requirements with the publisher.
- Access controls
- Access-control changes are not described here. Confirm the required roles and grants with the publisher.
- Removal and retained data
- A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
-
01
Prepare protected Composer access
Sign in to the account with active package access. Open its generated installation instructions and configure the protected Composer repository before running the commands below. Keep access credentials private. Open my package installation instructions
-
02
Require the package
composer require capell-app/dashboard-reports -
03
Install the extension
php artisan capell:extension-install capell-app/dashboard-reports -
04
Activate the package licence
In this site’s Admin, open Marketplace, find Dashboard Reports (capell-app/dashboard-reports), and activate its licence using the purchase licence key if requested. This activates the package you have already installed. Wait for the Marketplace operation to succeed before continuing; keep its queue worker running.
-
05
Report the installed package
php artisan capell:marketplace:heartbeat
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.9 Nov 10, 2026
- Recent activity
- 14 approved releases in the last 12 months
Review evidence for this release
Editorial reporting package reviewed with no defects found; its dashboard widgets are admin-only, check visibility before rendering, and expose no public output.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.9
- Approval date
- Nov 8, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Reports summarise publishing activity already recorded by the CMS; they do not add their own analytics collection.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
Version history
Showing the 10 most recent of 14 approved releases-
v1.1.9Nov 10, 2026 -
v1.1.8Nov 2, 2026 -
v1.1.7Oct 28, 2026 -
v1.1.6Oct 20, 2026 -
v1.1.5Oct 17, 2026 -
v1.1.4Oct 9, 2026 -
v1.1.3Oct 9, 2026 -
v1.1.2Oct 8, 2026 -
v1.1.1Oct 8, 2026 -
v1.1.0Oct 7, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.