Password Policy

Package docs status

This page is generated from public package documentation in capell-4/packages and the package manifest checked into the source repository.

Field	Value
Composer package	capell-app/password-policy
Package slug	password-policy
Product group	Capell Operations
Tier	premium
Bundle	operations
Runtime contexts	admin, console
Capell version	^4.0
Source repository	capell-app/packages
Source path	packages/password-policy
Docs source	packages/password-policy/docs
Manifest	capell.json

Password expiry, forced password changes, and password safety policy for Capell CMS.

At A Glance

• Package: capell-app/password-policy
• Namespace: Capell\PasswordPolicy\
• Surfaces: Filament admin, database
• Service providers: packages/password-policy/src/Providers/PasswordPolicyServiceProvider.php
• Capell dependencies: capell-app/admin, capell-app/core
• Third-party dependencies: laravel/framework, lorisleiva/laravel-actions, spatie/laravel-data, spatie/laravel-package-tools

Why It Helps Your Capell Workflow

• Adds password expiry, forced password changes, and password safety policy for Capell admin and user accounts.
• Helps operators enforce account hygiene without custom middleware in each host app.
• Pairs with login audit so security policy and authentication history can be reviewed together.

Best Used With

• Login Audit
• Diagnostics
• Document Lifecycle

What It Adds

• Password expiry, forced password changes, and password safety policy for Capell CMS.
• Settings-backed policy controls for password age, history, and forced changes.
• Admin-facing forced password change flow.

Built With

This package makes its Composer dependencies visible because they are part of the value proposition, not just plumbing. When an upstream package has a public repository, its linked preview card points readers back to the maintainers so their work gets proper credit.

Capell packages used here

• Capell Admin
• Capell Core

Open-source packages used here

• Laravel Actions - single-purpose action classes that keep package workflows out of controllers and Filament resources.
• Spatie Laravel Data - typed data objects for package boundaries, form state, settings, and structured results.
• Spatie Laravel Package Tools - Laravel package bootstrapping for config, migrations, commands, translations, and service provider setup.

Linked package previews

Code Map

Area	Path	Purpose
Actions	packages/password-policy/src/Actions	Domain operations. Test these directly where possible.
Data	packages/password-policy/src/Data	Structured payloads, form state, view models, and integration data.
Filament	packages/password-policy/src/Filament	Admin resources, pages, widgets, and settings UI.
HTTP	packages/password-policy/src/Http	Controllers, middleware, and request handling.
Providers	packages/password-policy/src/Providers	Registration, extension hooks, routes, migrations, and resources.
Resources	packages/password-policy/resources	Views, translations, assets, and package resources.
Config	packages/password-policy/config	Package configuration and publishable config.
Database	packages/password-policy/database	Migrations, seeders, and settings migrations.
Tests	packages/password-policy/tests	Package-level Pest coverage.

Admin Surface

• Pages: ForcedPasswordChangePage, PasswordPolicySettingsPage.
• Settings: PasswordPolicySettings.

Data And Persistence

• Migrations: 2026_05_10_190863_01_add_password_policy_columns_to_users_table.php, 2026_05_10_190863_02_create_password_policy_password_histories_table.php.
• Settings migration: 2026_05_10_190864_01_create_password_policy_settings.php.
• Config: packages/password-policy/config/capell-password-policy.php.
• Data objects live in src/Data/; use them for payloads, form state, and view models.

Extension Points

• Register Capell extension points, routes, migrations, settings, render hooks, and resources from service providers.

Install And Setup

• Install with composer require capell-app/password-policy in the host Capell application.
• Run the host application package install flow so both database/migrations and database/settings files are published before migrations run.
• In this repository, verify package changes with vendor/bin/pest; do not use php artisan.

Docs

• docs index
• overview.md
• screenshots.json
• credits-and-acknowledgements.md

Testing

Run package tests from the repository root:

vendor/bin/pest packages/password-policy/tests --configuration=phpunit.xml

Maintenance Notes

• Put behaviour changes in src/Actions/; UI classes, commands, and controllers should call actions instead of owning domain logic.
• Use package Data classes at boundaries instead of passing anonymous arrays between layers.