> For the complete documentation index, see [llms.txt](https://skaleptyltd.gitbook.io/build-solution/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://skaleptyltd.gitbook.io/build-solution/product-guides/system/permission.md).
# Permission
{% hint style="info" %}
The system provides users with the ability to perform three main actions on permissions for different user types:
1. Create: Users can create new permissions, defining the access levels for various user types.
2. Edit: Users have the option to modify existing permissions, making changes to the access rights of different user types.
3. Delete: Users can remove permissions, effectively revoking specific access privileges for different user types.
{% endhint %}
{% tabs %}
{% tab title="Navigation to the page" %}
* Login as an Admin > System > Permission
In the user interface, the user has the option to choose how many records they want to see on a single page. They can set a specific number to control the amount of information displayed at once.
Furthermore, the system allows the user to filter the records by typing the permission name in a search box. As they type, the relevant records that match the permission name will be dynamically filtered and displayed, making it easier for the user to find specific permissions quickly.
***
**Create Permission**
When the user clicks on the "Create Permission" button, they are immediately taken to a form where they can input the necessary information to create a new permission.
Create Permission form
The "Create Permission" form consists of two fields: a text field for entering the permission name and a dropdown menu with two options: "Role" and "User." The user can choose between these options to determine whether to assign permission to a specific user role or to an individual user.
In addition to these fields, there are multiple checkboxes available for selecting user roles. Users can choose multiple user roles while creating the permission, allowing them to assign the permission to multiple roles at once.
When the user clicks on the "Submit" button, they are redirected back to the permissions page. A success banner appears, indicating that the permission created was successful.
> Important points to think about when making permissions:
>
> * There are two kinds of permissions: "ROLE" and "USER".
> * When you name a permission, you can use the format you're already using (like "view\.permissions").
> * If you choose "ROLE" as the type and pick roles at the bottom, the permission you make will be given to those roles right away.
Create Permission success banner
***
**Edit Permission**
Edit Permission form
When the user clicks on the "Edit" button of a specific permission record, they are directed to the "Edit Permission" form. In this form, the name and type fields are automatically filled with the existing values of the permission. However, the user can update these fields with new values.
Unlike the "Create Permission" form, the checkboxes for selecting user roles are not visible in the "Edit Permission" form.
After the user updates the permission details and clicks on the "Submit" button, they are redirected back to the permissions page. A success banner appears, indicating that the permission update was successful.
Update success banner
In the "Edit Permission" form, just like in the "Create Permission" form, all the fields are required to be filled out. This means that the user must provide information for all the fields before they can successfully update the permission details.
***
**Delete Permission**
When the user clicks on the "Delete" button of a permission record, a pop-up message will appear asking for confirmation. If the user clicks on the "OK" button in the pop-up, the record will be deleted, and a success banner will be displayed to confirm the successful deletion.
On the other hand, if the user clicks on the "No" button in the pop-up, nothing will happen to the record, and it will remain unchanged. The deletion process will be canceled, and the user can continue without deleting the record.\
Delete confirmation message
Delete success banner
{% endtab %}
{% tab title="Database tables and queries" %}
Below are the related DB tables:
* permission
{% endtab %}
{% tab title="Paths" %}
#### Function Path
```
app/Http/Controllers/Admin/PermissionController.php
```
{% endtab %}
{% endtabs %}
*Why do permission names have a '.' in between? And the '.' in the permission name is not displaying in create role form?*
*Can we sort the permissions table??*
Admin users have the ability to create, edit, and delete permissions that can be assigned to user roles.
*Who else is permitted to create, edit, and delete permissions?*
*What is the purpose of the 'Type' dropdown?*
*What is the purpose of letting the user select roles if creating permission type is User?*
*Why are checkboxes not displaying in the edit form?*
