Document Lifecycle
Know which document version someone accepted.
- Version
- 1.1.10
- Released
- 10 November 2026
- Requires
- Publishing Studio
- Licence
- Commercial
Price £39.00
Check access and installationCheck your application before checkout
What it solves
The problem
Our compliance team cannot readily establish which document version someone accepted.
What your site gets
Our team has a record of published document versions and their acceptance history.
Questions buyers ask
- What evidence is kept for each publication?
- Published versions are immutable and carry content hashes, with an acceptance history for each version.
- When might a document require acceptance again?
- A changed document can require acceptance again.
- Who can see document history?
- An optional Customer Portal contribution exposes relevant history to signed-in customers.
Use it in your project
Publish a controlled document as a recorded version, then retain acceptance evidence for that version. A later revision can require a fresh acceptance.
Picture it on your site
For a controlled policy document, decide which version people must accept and what evidence the team needs to retain. Try a revision as well as the first publication. Versioned acceptance gives the process a clear reference; the organisation remains responsible for its document wording, retention decisions and any applicable legal requirements.
6 captures
Manage access and accountability
- Keep versioned publications and content hashes.
- Record acceptances and document review dates.
Is this right for your project?
Decide what is being protected
Write down the protected resource, the people who should reach it and the decision that grants or removes access. That makes the extension part of a clear application policy instead of an isolated setting. Check the supported controls against your actual routes and records. The package does not decide your organisation's policy, and it should not be treated as a substitute for the rest of your security review.
Check refusal as well as access
Test an authorised person, an unauthorised person and a changed or revoked permission. Inspect both the response and the recorded activity where the package supplies it. Your application still owns authentication, role assignment and any routes outside the package's protection boundary. A visible admin control is not enough to establish that every public path is covered.
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.
Works with Document Lifecycle
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, command-line operations. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. Uses package-local configuration and Capell metadata needed to enable the feature.
- Background work
- Scheduled background work is declared. Keep the host scheduler running and check the release documentation for queue workers, frequencies and pruning configuration.
- Access controls
- Package access controls are declared. Review role grants and the host authorisation configuration before allowing users into the new workflow.
- 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/document-lifecycle -
03
Install the extension
php artisan capell:extension-install capell-app/document-lifecycle -
04
Activate the package licence
In this site’s Admin, open Marketplace, find Document Lifecycle (capell-app/document-lifecycle), 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.10 Nov 10, 2026
- Recent activity
- 14 approved releases in the last 12 months
Review evidence for this release
Document lifecycle package reviewed with no defects found; it adds review and retention states to editorial workflows without introducing any public endpoint.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.10
- 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
- Lifecycle states apply to content managed through the publishing workflow, so documents created outside that workflow are not tracked. Cross-package integration was not exercised by this per-package review; the local suites used SQLite, and live browser flows and server-database behaviour were not exercised. The MySQL/MariaDB-specific timestamp-repair branch was reviewed in source but was not executed by this SQLite attestation run.
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.10Nov 10, 2026 -
v1.1.9Nov 2, 2026 -
v1.1.8Oct 28, 2026 -
v1.1.7Oct 20, 2026 -
v1.1.6Oct 17, 2026 -
v1.1.3Oct 9, 2026 -
v1.1.2Oct 8, 2026 -
v1.1.1Oct 8, 2026 -
v1.1.0Oct 7, 2026 -
v1.1.0-beta.45Oct 4, 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.