Released

Access Gate

Decide who can open protected pages and downloads.

Version: 1.0.51
Released: 20 October 2026
Licence: Commercial

Price £29.00

Check access and installation

A genuine Access Gate product screenshot. Open the workflow gallery for its full description. — Review protected areas, their policies and current registration and grant counts.

Price and access
Review the price, licence and availability before deciding what to adopt.
Your workflow
Read how the package is used and what your application needs to provide.
Product captures
Review the available captures and see which part of the workflow each screen demonstrates.
Capabilities
See which jobs this extension supports and which parts it adds to your site.
Project fit
Decide what this removes from your workload and what your application still needs to supply.
Installation
Check the setup steps before adding the package to a project.
Release evidence
Review the available release, maintenance and package-review information.

Usage

Use it in your project

Use Access Gate when content needs an approval or access grant before a visitor can see it. Staff can review requests and revoke access from the admin.

Picture it on your site

For a partner resource area, decide which pages and downloads need protection, who approves requests and when a grant should end. Try that journey with an approved account and an unapproved visitor before opening it to partners. The useful outcome is a clear access process, not another password shared by the whole team.

11 captures

Access Gate access areas with active and paused states, policies, registration counts and Edit actions. — Review protected areas, their policies and current registration and grant counts.

Access Gate area edit form with identity, approval and registration settings. — Configure an access area using its native admin form.

Access Gate registrations with pending, approved, claimed and rejected states and lifecycle dates. — Review visitor registrations, their state and lifecycle dates, with row actions.

Access Gate active grants with start and expiry dates and Revoke actions. — Review active grants and revoke access from the native admin table.

Access Gate claim links with Active and Claimed states, expiry and consumption dates. — Review approval links and see whether and when each claim was consumed.

Access Gate browser session with its state, lifetime, user agent and Revoke action. — Review a browser session and revoke its access when needed.

Access Gate audit events showing registration and grant creation history. — Trace registration and grant creation in the native audit table.

Public Access Gate email request form for private release access. — Visitors request access through the native public email form.

Access Gate claim-link confirmation form before token consumption. — Visitors confirm a claim link before its one-time token is consumed.

Native Access Gate request button on a public release-preview teaser with the example contact email shown. — The existing request CTA posts the displayed contact email to Access Gate; visitors can choose the full request form to supply a different address.

Native Site Lockdown password form and account sign-in link on a private site, using its fixed dark presentation. — The real HTTP 401 challenge offers shared-password entry and the existing account sign-in link before private content renders.

Included

Manage access and accountability

Approve, reject, expire or revoke access grants.
Review requests and access activity in one place.

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.

Licence £29.00 / 12 months

+ VAT where applicable

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

Your renewal price stays locked while you renew continuously, including during the grace period. After a full lapse, renewal uses the current list price.

Review site impact

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. Add a free package to your account, then review compatibility and site impact before installing it.

Open the live demo

Explore the available extensions on the demo site.

Details

At a glance

Version: 1.0.51
Released: 20 October 2026
Compatibility: Capell 4.x; Laravel 13.x; Filament 5.x
Support: Standard support
Data access: Reads and writes Capell content structures required by the package; public output receives rendered content only.
Licence: Commercial

Installation impact

Before you install

Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.

01

Require the package

composer require capell-app/access-gate
02

Install the extension

php artisan capell:extension-install capell-app/access-gate

Release and review evidence

Maintenance

Release activity stays visible

These dates come from approved package releases, so you can see the release trail before installing.

Latest approved release: v1.0.51 Oct 20, 2026
Recent activity: 23 approved releases in the last 12 months

Capell reviewed

Review evidence for this release

Access control and audit package reviewed with no defects found beyond a cosmetic migration-history quirk.

Review reduces risk, but it is not a permanent security guarantee.

Automated checks passed

AI-assisted analysis completed

Human sign-off completed

Reviewed version: 1.0.51
Approval date: Oct 19, 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

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.

Read the full Capell review method

Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.

Changelog

Release notes and maintenance evidence

Total downloads: 0
Last downloaded: No downloads yet

Version history

10 releases

v1.0.51
Oct 20, 2026
v1.0.50
Oct 17, 2026
v1.0.49
Oct 9, 2026
v1.0.48
Oct 9, 2026
v1.0.47
Oct 8, 2026
v1.0.46
Oct 8, 2026
v1.0.45
Oct 7, 2026
v1.0.44
Oct 4, 2026
v1.0.43
Oct 1, 2026
v1.0.42
Sep 29, 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?

Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.

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.

Access Gate