Login Audit
Login Audit keeps a clear Capell access history: logins, failed attempts, logouts, devices, and sessions.
What Login Audit helps you do
This private package is outside the Released and Beta channels, so no public install path is available.
Workflow screenshots
6 capturesLogin Audit keeps a clear Capell access history: logins, failed attempts, logouts, devices, and sessions.
Admins can review account activity for support cases and security investigations without piecing together server logs.
Retention controls keep audit data useful without storing it forever by default.
Use it when Capell needs accountable authentication history close to the users and roles it describes.
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 Login Audit adds when enabled.
- Audit
- Authentication
- Operations
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/login-audit -
02
Register the extension
php artisan capell:extension:enable login-audit -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Login Audit
Switch the evaluation lens to see how different roles should assess this package before installing it.
A tamper-resistant record of who got in — what to verify
Sign in from two accounts and verify that both events appear with correct time and context. Attempts to rewrite the earlier record should fail or leave the original immutable evidence intact.
Read more Show less
Evidence to request: The audit records sign-ins, flags suspicious activity and tracks each admin's last-seen time. Toggle IP capture to verify the GDPR-sensitive setting, then confirm that historical events remain immutable.
Alternative fit: It records and signals, it does not defend. For active threat response site owners would still bring in a developer and proper security tooling, so site owners treat it as evidence, not a shield.
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.
