Overridable controllers, policies and default permissions (RBAC, multi-auth)

Controllers overridable from config or the container
Routes registered by a macro so apps choose prefix, middleware and guard
Nothing assumes the web guard or App\Models\User
A Policy and default permissions registered through javaabu/permissions' registration API
Policies overridable from config or Gate::policy()
Feature tests for authorization and for two guards

Builder, entries and fill routes with Blade views

Tests for filling, entries, import and export, and authorization with…

Done.

Overridable. Controllers (forms, sections, fields, entries, fill, assistant) come from config or route options and have hooks.
Routes. Route::formBuilder() and Route::formBuilderFill() take guard, prefix, name and middleware.
Multi-auth. Authors and submitters are morphs, and authorization uses the route guard's user.
Policies. FormPolicy and FormEntryPolicy check seven permissions registered with javaabu/permissions, and can be overridden from config, permissions.policies or Gate::policy().
Tests. Guests, missing permissions, viewer and editor-only rights, locked forms, two guards (web and web_admin), and policy and controller overrides.

Docs: docs/basic-usage/permissions.md

Navigation Menu