- How do I install Betta Terms in a Laravel application?
- Install the package with Composer using composer require e2d2-dev/betta-terms. Then follow the README to publish its configuration, views, and migrations as needed, and run your database migrations. Because it integrates with FilamentPHP, check the package docs for any panel registration or middleware steps.
- Does Betta Terms work with FilamentPHP panels?
- Yes. Betta Terms is described as a terms and conditions guard for FilamentPHP, so it is intended to help enforce consent around Filament-powered applications. It provides routes, views, middleware, and model traits that you wire into your panel or application. Confirm the supported Filament and Laravel versions in the package composer constraints before installing.
- How does versioned terms and privacy policy acceptance work?
- Betta Terms lets you publish versions of your terms and privacy policy and record which version each user accepted. Those consent records are designed to be audit-friendly, so you can review acceptance history rather than only a single boolean flag. When you publish a new version, users can be required to accept it before continuing.
- Can I require users to accept terms before accessing my app or Filament panel?
- Yes. The package includes middleware intended to require consent before access, so you can protect routes or panel areas until the current terms version has been accepted. You configure where that middleware applies and how users are redirected to the acceptance flow. Review the published configuration to match your application’s access rules.
- Which Laravel versions does Betta Terms support?
- The exact Laravel and PHP version constraints are defined in the package composer.json and may change between releases. Check those constraints and the README before adding it to an existing application, especially if you are on an older Laravel version. Also verify FilamentPHP compatibility because the package is built as a Filament terms guard.
- How do I customize the terms routes and views?
- Betta Terms provides configurable routes and views, so you can adjust URLs and publish the views to override their markup. Start by publishing the package configuration and view files according to the README, then edit the published copies in your application. Keep your customizations in your app rather than vendor files so they survive Composer updates.
- How are user consent records stored for auditing?
- The package stores acceptance records so you can show which user accepted which terms version and when. It is intended to produce audit-friendly consent records rather than only tracking a general accepted flag. Review the published migrations and model before production use so the stored data matches your compliance requirements.
- Can I use Betta Terms outside FilamentPHP?
- Betta Terms is designed primarily as a terms and conditions guard for FilamentPHP, so its routes, views, and middleware are oriented around that use case. Some pieces, such as model traits and middleware, may be reusable in a regular Laravel application, but you should confirm the integration path in the documentation. If you need a framework-agnostic consent layer, evaluate whether the Filament assumptions fit your app.
- How should I test terms acceptance in my Laravel tests?
- Test the protected route or Filament page as a user who has not accepted the current terms, then assert that access is blocked or redirected to the acceptance flow. After recording acceptance, assert that the user can access the protected area and that the consent record exists for the correct version. Use your normal Laravel HTTP and database assertions, and check the package README for any provided testing helpers.
- Is Betta Terms actively maintained, and what should I check before using it in production?
- Review the GitHub repository and Packagist release history for recent commits, tagged releases, open issues, and compatibility with your Laravel and Filament versions. Also check the license, migration impact, and whether the consent records meet your legal or audit requirements. If maintenance activity is limited, compare it with building a small custom middleware and acceptance table or with other actively maintained consent packages.