Feature Flags

You can force-enable or disable parts of the backend with TinyAuthBackend.features. This is useful when you only want the classic TinyAuth adapter functionality exposed in the UI.

'TinyAuthBackend' => [
    'features' => [
        'allow' => true,
        'acl' => true,
        'roles' => true,
        'resources' => false,
        'scopes' => false,
    ],
],

Known feature keys

Key	Section	Manages
allow	Allow (Public Actions)	Actions reachable without authentication
acl	ACL Matrix	Controller/action role permissions
roles	Roles	Role aliases, ordering, and hierarchy
resources	Resources	Entity-level abilities
scopes	Scopes	Reusable field-comparison conditions

A disabled feature is removed from the navigation and its controllers reject requests, so you can trim the backend down to exactly the surface you use.

Adapter-only setups

For a classic TinyAuth setup that only stores allow and acl in the database, disable resources and scopes — see the Adapter-Only strategy.

Inspecting flags at runtime

The FeatureService resolves which sections are enabled and builds the navigation:

use TinyAuthBackend\Service\FeatureService;

$service = new FeatureService();
$enabled = $service->isEnabled('resources');
$items = $service->getNavigationItems();