Download the PHP package wnikk/laravel-access-ui without Composer

On this page you can find all versions of the php package wnikk/laravel-access-ui. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package laravel-access-ui

Laravel Access Control Rules

Laravel Access Control Rules UI

The administration panel of wnikk/laravel-access-rules 3.x: rules, owners, permissions with conditions, inheritance, the explanation of one check, a health check of stored conditions, XACML export and import, and one card for a page of your application that shows an account.

PHP Version Require Total Downloads

One script and one stylesheet, published into public/. No CSS framework, no CDN, no web font, no asset pipeline to agree with.

And no knowledge of your application. The panel reads and writes the tables of the core and nothing else. It never loads or names a model of yours to find an owner. Integration is one expression, the owner id, which the core already gives you through the trait it asks you to add to the user model.

And no logic of access of its own. Every write goes through the API of the core, every decision comes from its explain(). What the panel shows is what the core will do.

What you get

Screen What it does
Rules the names your code checks against, with their origin: rules of code keep their name and condition, rules of the panel are created for names code builds at run time
Owners the rows that hold permissions, paged and searched, whatever their type
Permissions for one owner, rule by rule: every permit and prohibition that reaches it, each with its condition; Allow, Forbid, With condition
Inheritance who inherits from whom
Why? one check explained: every permission that took part, the one that decided, what its condition read
Health what acr:lint and acr:doctor find, with "fix", "delete stray rows" and a cache button
XACML download the policy; upload one and see what it would change before importing
The card on a user page: what the account inherits from, what may be assigned, four numbers

New in 3.0

Kept from 2.0: styles under wacu-, light and dark, a layout of yours or a bare page, screens with enabled, write and ability, entities as configuration, the card in one line, one JSON envelope, translations key by key.

Requirements

For an older application: composer require wnikk/laravel-access-ui:^2.0.

Install

The second command is required: it copies the bundle to public/vendor/accessui. Repeat it with --force after every upgrade.

Then turn the routes on. Nothing is registered until both keys are set, because these routes hand out permissions and an install nobody configured must expose nothing:

['web', 'auth'] alone lets every signed-in account grant itself everything. Name what marks an administrator in your application: a Gate (can:manage-access), a rule of the core (can:system.access.manage), or a middleware of yours (admin).

Open /access-control. To render the panel inside your admin area, name your layout:

The card on a user page

What this account inherits from, a dropdown of what may still be assigned, a remove button per row, and four numbers: inherited rows, own rows, rows that depend on the record, prohibitions. Own rows on an account with nothing assigned mean somebody hand-tuned it. The line renders nothing while the routes are off, so it is safe in every environment.

Whether the card may change anything is decided on the server, per request and per owner: config widget.write and a Gate ability that receives the owner of the card. The page gets what the card uses and nothing else.

Documentation

The language of conditions, the priority of permissions and the API of the core are documented by the core: conditions, basic usage.

Seeding rules

The panel manages rules and does not invent the ones your code checks. Create those in a migration or a seeder of the core:

Restyling and translations

Put that before the bundle and the first render is translated; accessUi.addMessages('de', {...}) after it adds or corrects strings. Keys are in resources/js/lang/en.json; English is the fallback key by key. Refusals of the core are translated on the server: vendor:publish --tag=accessUi-lang.

Building from source

Output is dist/accessUi.js and dist/accessUi.css, an IIFE a page loads with a plain <script src>. Vue is bundled in: the panel works on a machine with no route to the internet. dist/ is committed, so installing needs no Node.

For AI coding agents

The package ships a Laravel Boost guideline and a skill (resources/boost/), installed into an application by php artisan boost:install, and docs/llms.txt as a map of the documentation. Agents working on this repository read AGENTS.md.

Caveats

No audit trail. The core fires AccessChanged on every change; listen to it for a log of who changed what.

No rate limiting. Add throttle: to the middleware of the group when more than a few administrators reach it.

Deleting an owner row is for good. Its permissions and links go with it, and everyone who inherited from it loses what it held.

Contributing

Please report any issue you find in the issues page. Pull requests are more than welcome.

License

The MIT License (MIT). Please see License File for more information.


All versions of laravel-access-ui with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
illuminate/contracts Version ^13.0
illuminate/database Version ^13.0
illuminate/http Version ^13.0
illuminate/routing Version ^13.0
illuminate/support Version ^13.0
illuminate/validation Version ^13.0
illuminate/view Version ^13.0
wnikk/laravel-access-rules Version ^3.3.15
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wnikk/laravel-access-ui contains the following files

Loading the files please wait ...