https://github.com/wnikk/laravel-access-rules
Simple system of ACR (Access Control Rules) for Laravel, with roles, groups, unlimited inheritance and possibility of multiplayer use.
https://github.com/wnikk/laravel-access-rules
acl acr authorization laravel multiuser permissions php rbac roles secure
Last synced: 7 months ago
JSON representation
Simple system of ACR (Access Control Rules) for Laravel, with roles, groups, unlimited inheritance and possibility of multiplayer use.
- Host: GitHub
- URL: https://github.com/wnikk/laravel-access-rules
- Owner: wnikk
- License: mit
- Created: 2023-02-08T19:25:48.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-10-15T16:09:56.000Z (over 1 year ago)
- Last Synced: 2025-02-21T15:04:46.565Z (over 1 year ago)
- Topics: acl, acr, authorization, laravel, multiuser, permissions, php, rbac, roles, secure
- Language: PHP
- Homepage:
- Size: 108 KB
- Stars: 9
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Access Control Rules (Laravel Permissions Package)
[](//packagist.org/packages/wnikk/laravel-access-rules)
[](//codeclimate.com/github/wnikk/laravel-access-rules)
[](//packagist.org/packages/wnikk/laravel-access-rules)
[](//packagist.org/packages/wnikk/laravel-access-rules)
[](//packagist.org/packages/wnikk/laravel-access-rules)
[](//packagist.org/packages/wnikk/laravel-access-rules)
## What does Access Control Rules support?
- Multiple user models.
- Multiple permissions can be attached to users.
- Multiple permissions can be attached to groups.
- Permissions verification.
- Permissions caching.
- Events when permissions are attached, detached or synced.
- Multiple permissions can be attached to user or group.
- Permissions can be inherited with unlimited investment from users and groups.
- Laravel gates and policies.
## Visual Interface
The visual interface for managing access control rules and permissions can be found at [this link](https://github.com/wnikk/laravel-access-ui).
It offers an intuitive and user-friendly environment for administrators to define roles, assign permissions, and configure access rules.
For detailed usage examples and instructions, refer to the [example repository](https://github.com/wnikk/-laravel-access-example).
## Documentation, Installation, and Usage Instructions
See the [documentation](https://github.com/wnikk/laravel-access-rules/tree/master/docs) for detailed installation and usage instructions.
## Versions & Dependencies
| Laravel Access Control Rules | PHP | Laravel |
|------------------------------|-----------|---------|
| 2.x+ | 7.4 - 8.4 | 8 - 12 |
| 1.x | 7.1 - 7.3 | 5.5 - 8 |
## You can install the package using composer:
```bash
composer require wnikk/laravel-access-rules
```
See the [installation page](https://github.com/wnikk/laravel-access-rules/blob/main/docs/installation.md) for detailed.
## What It Does
This package allows you to manage user permissions and groups (instead roles) in a database.
Once installed you can do stuff like this:
```php
use Wnikk\LaravelAccessRules\AccessRules;
// Add new rule permission
AccessRules::newRule('articles.edit', 'Access to editing articles');
```
```php
// Adding permissions to a user
$user->addPermission('articles.edit');
```
Or you can inherit the rights from another user or groups
```php
// According to the existing user from object
$user->inheritPermissionFrom(User::find(1));
// By identifier
$user->inheritPermissionFrom(User::class, 1);
// From the group
$user->inheritPermissionFrom('Group', 1);
```
Because all permissions will be registered on **Laravel's gate**, you can check if a user has a permission with Laravel's default `can` function:
```php
$user->can('articles.edit');
```
Or without model:
```php
$acr = new AccessRules;
$acr->setOwner('AnotherAnySystemUser', 'UserID-From-Any-System-FF01');
$check = $acr->can('articles.edit');
if (!$check) {abort(403);}
```
Examples of how can be used in more detail described in [Basic Usage](https://github.com/wnikk/laravel-access-rules/blob/main/docs/basic-usage.md) section.
## Opening an Issue
Before opening an issue there are a couple of considerations:
* You are all awesome!
* Pull requests are more than welcome.
* **Read the instructions** and make sure all steps were *followed correctly*.
* **Check** that the issue is not *specific to your development environment* setup.
* **Provide** *duplication steps*.
* **Attempt to look into the issue**, and if you *have a solution, make a pull request*.
* **Show that you have made an attempt** to *look into the issue*.
* **Check** to see if the issue you are *reporting is a duplicate* of a previous reported issue.
* **Following these instructions show me that you have tried.**
* Please be considerate that this is an open source project that I provide to the community for FREE when opening an issue.
## Alternatives
- [spatie/laravel-permission](https://github.com/spatie/laravel-permission) takes a slightly different approach to its features.
- [ultraware/roles](https://github.com/ultraware/roles) It not supported and transferred to archive.
- [santigarcor/laratrust](https://github.com/santigarcor/laratrust) implements team support.
- [zizaco/entrust](https://github.com/zizaco/entrust) offers some wildcard pattern matching.
## License
The MIT License (MIT). Please see [License File](LICENSE.md) for more information.