Capell Admin
Capell Admin gives editors a Filament workspace for structured content, settings, roles, publishing, and CMS operations.
What Capell Admin helps you do
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Workflow screenshots
6 capturesCapell Admin gives editors a Filament workspace for structured content, settings, roles, publishing, and CMS operations.
Day-to-day site work stays in one admin rather than scattered tools.
Packages contribute resources into the same shell so the experience stays coherent.
Use it when Capell needs a focused editorial and operations workspace.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Capell Admin adds when enabled.
- Filament
- Admin
- Publishing
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/admin -
02
Register the extension
php artisan capell:extension:enable admin -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Capell Admin
Switch the evaluation lens to see how different roles should assess the Capell platform foundation.
Capell Admin: evidence for the site owner role
Install one healthy and one deliberately misconfigured extension, then compare their risk scores. The admin should explain the live health, runtime and database signals behind each 0-to-100 result.
Read more Show less
Inspect this behaviour: Installed extensions receive a 0-to-100 risk score derived from live health, runtime and database signals rather than a static label. Compare a healthy and misconfigured package and require the contributing signals to be visible.
A different tool may fit when: If it is just site owners making occasional low-stakes edits, this is more insight than site owners need. The value shows up once the site has several extensions and more than one person touching it, and site owners still keep a developer for upkeep.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
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 hosts paid marketplace checkout and 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 licence, receipt, support history, and future install access. 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.
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.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
