PHPackages                             filament/spatie-laravel-settings-plugin - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Admin Panels](/categories/admin)
4. /
5. filament/spatie-laravel-settings-plugin

ActiveLibrary[Admin Panels](/categories/admin)

filament/spatie-laravel-settings-plugin
=======================================

Filament support for `spatie/laravel-settings`.

v5.6.7(1mo ago)1143.0M↓21.7%1120MITPHPPHP ^8.2

Since Nov 25Pushed 1w ago5 watchersCompare

[ Source](https://github.com/filamentphp/spatie-laravel-settings-plugin)[ Packagist](https://packagist.org/packages/filament/spatie-laravel-settings-plugin)[ Docs](https://github.com/filamentphp/filament)[ RSS](/packages/filament-spatie-laravel-settings-plugin/feed)WikiDiscussions 5.x Synced 2d ago

READMEChangelogDependencies (10)Versions (1087)Used By (20)

Filament Spatie Settings Plugin
===============================

[](#filament-spatie-settings-plugin)

Installation
------------

[](#installation)

Install the plugin with Composer:

```
composer require filament/spatie-laravel-settings-plugin:"^5.0" -W
```

Preparing your page class
-------------------------

[](#preparing-your-page-class)

Settings pages are Filament pages that extend the `Filament\Pages\SettingsPage` class.

This package uses the [`spatie/laravel-settings` package](https://github.com/spatie/laravel-settings) to store and retrieve settings via the database.

Before you start, create a settings class in your `app/Settings` directory, and a database migration for it. You can find out more about how to do this in the [Spatie documentation](https://github.com/spatie/laravel-settings#usage).

Once you've created your settings class, you can create a settings page in Filament for it using the following command:

```
php artisan make:filament-settings-page ManageFooter FooterSettings
```

In this example, you have a `FooterSettings` class in your `app/Settings` directory.

In your new settings page class, generated in the `app/Filament/Pages` directory, you will see the static `$settings` property assigned to the settings class:

```
protected static string $settings = FooterSettings::class;
```

Building a form
---------------

[](#building-a-form)

You must define a form schema to interact with your settings class inside the `form()` method.

Since the [Form Builder](https://filamentphp.com/docs/forms) is installed in the Panel Builder by default, you may use any form [fields](https://filamentphp.com/docs/forms) or [layout components](https://filamentphp.com/docs/schemas/layout) you like:

```
use Filament\Forms\Components\Repeater;
use Filament\Forms\Components\TextInput;
use Filament\Schemas\Schema;

public function form(Schema $schema): Schema
{
    return $schema
        ->components([
            TextInput::make('copyright')
                ->label('Copyright notice')
                ->required(),
            Repeater::make('links')
                ->schema([
                    TextInput::make('label')->required(),
                    TextInput::make('url')
                        ->url()
                        ->required(),
                ]),
        ]);
}
```

The name of each form field must correspond with the name of the property on your settings class.

The form will automatically be filled with settings from the database, and saved without any extra work.

Authorization
-------------

[](#authorization)

By default, no users are restricted from accessing settings pages. To prevent a page from being accessed altogether, define a `canAccess()` method in the page class, and return `true` or `false` based on the user's permissions:

```
public static function canAccess(): bool
{
    return auth()->user()->isAdmin();
}
```

If the user has access to the page, you can also prevent them from editing the settings. This is useful if a user needs to be able to check the current state of the settings, but not change them. In this case, the settings form would be "disabled" and read-only. Define the `canEdit()` method in the page class, and return `true` or `false` based on the user's permissions:

```
public static function canEdit(): bool
{
    return auth()->user()->isAdmin();
}
```

> Note: `canEdit()` only gates saving — it does not prevent a user from loading the page and reading every field's current value. If the settings themselves are sensitive (API keys, internal flags, etc.), restrict viewing with `canAccess()` (and/or route middleware) instead of relying on `canEdit()`.

Publishing translations
-----------------------

[](#publishing-translations)

If you wish to translate the package, you may publish the language files using:

```
php artisan vendor:publish --tag=filament-spatie-laravel-settings-plugin-translations
```

###  Health Score

70

—

ExcellentBetter than 100% of packages

Maintenance95

Actively maintained with recent releases

Popularity58

Moderate usage in the ecosystem

Community29

Small or concentrated contributor base

Maturity82

Battle-tested with a long release history

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~2 days

Total

1086

Last Release

21d ago

Major Versions

v4.8.0 → v5.1.12026-01-23

v4.10.2 → v5.4.52026-03-17

v4.11.1 → v5.6.12026-04-21

v4.11.4 → v5.6.42026-05-20

v4.12.0-beta1 → v5.6.62026-05-22

PHP version history (3 changes)v2.4.45PHP ^8.0

v3.0.0-alpha92PHP ^8.1

v4.0.0-alpha3PHP ^8.2

### Community

Maintainers

![](https://www.gravatar.com/avatar/d5513b5defa6f680b8db229a305abf62d4e70f3e943b0da57dd5b303095c50c6?d=identicon)[DanHarrin](/maintainers/DanHarrin)

---

Top Contributors

[![danharrin](https://avatars.githubusercontent.com/u/41773797?v=4)](https://github.com/danharrin "danharrin (123 commits)")

### Embed Badge

![Health badge](/badges/filament-spatie-laravel-settings-plugin/health.svg)

```
[![Health](https://phpackages.com/badges/filament-spatie-laravel-settings-plugin/health.svg)](https://phpackages.com/packages/filament-spatie-laravel-settings-plugin)
```

###  Alternatives

[finity-labs/fin-mail

A powerful email template manager and composer for Filament with dynamic token replacement, template versioning, and inline email sending.

284.5k1](/packages/finity-labs-fin-mail)[rawilk/profile-filament-plugin

Profile & MFA starter kit for filament.

3914.6k](/packages/rawilk-profile-filament-plugin)[tapp/filament-lms

193.4k](/packages/tapp-filament-lms)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)