Skip to main content
Subscribd includes a lightweight, Blade-based admin panel that gives you a real-time view of your billing data without setting up Filament or a separate dashboard tool. The panel shows monthly recurring revenue (MRR), active subscription counts, a plan breakdown, and controls to manage individual subscribers. You configure its URL, middleware, and enabled state from config/subscribd.php.

​
What the panel shows

MRR

Monthly recurring revenue calculated from all active and trialing subscriptions.

Active subscriptions

A live count of subscriptions in active and trialing status.

Plan breakdown

Per-plan subscriber counts so you can see which plans are most popular.

Per-subscriber management

Look up any subscriber, view their invoices, and cancel or resume their subscription.

​
Default URL

The panel is accessible at /subscribd/admin by default. You can change this path in the config.

​
Enabling the panel

Add the following block to config/subscribd.php to enable the admin panel and configure its URL and middleware:
config/subscribd.php
'admin' => [
    'enabled'    => true,
    'path'       => 'subscribd/admin',
    'middleware' => ['web', 'auth', 'can:manage-billing'],
],
The can:manage-billing middleware is a Laravel Gate check. Define the manage-billing ability in your AuthServiceProvider (or AppServiceProvider in Laravel 12) to control which users have access:
app/Providers/AppServiceProvider.php
use Illuminate\Support\Facades\Gate;

Gate::define('manage-billing', function ($user) {
    return $user->isAdmin();
});
You can replace can:manage-billing with any middleware your app already uses for admin access, such as role:admin from a package like Spatie Laravel Permission.

​
Disabling the panel

If you use the Filament resources for subscription management, disable the standalone panel to avoid a duplicate UI:
config/subscribd.php
'admin' => [
    'enabled' => false,
],
When enabled is false, Subscribd does not register any admin routes, so the /subscribd/admin URL returns a 404.
The panel is intended for internal use by your team. Always protect it with appropriate middleware. The default can:manage-billing gate is a starting point — verify that it matches your application’s authorization model before deploying to production.