> For the complete documentation index, see [llms.txt](https://ledsak.gitbook.io/docs-for-ledsak/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ledsak.gitbook.io/docs-for-ledsak/staff-management/roles-and-permissions.md).

# Roles and Permissions

### Defining Roles

Roles are predefined categories assigned to staff members based on their responsibilities. Each role has a set of permissions associated with it. Below are the key steps for defining roles:

#### 1.1 Identify Key Roles

* **Super Admin**: Full access to all systems and settings.
* **Manager**: Access to team management tools, reports, and approvals.
* **Team Member**: Access to specific tasks, tools, and limited resources.
* **Support Staff**: Access to support tools and customer interaction resources.
* **Guest**: Limited access to specific areas or tools for temporary use.

#### 1.2 Role Documentation

Each role should include:

* **Role Name**
* **Access Requirements**

### 2. Assigning Permissions

Permissions define what actions a role can perform. These permissions should align with the responsibilities of the role.

#### 2.1 Permission Categories

* **(Can View) Read Access**: Ability to view data.
* **(Can Add) Write Access**: Ability to create or modify data.
* **(Can Edit, Can Delete etc.) Execute Access**: Ability to run specific functions or processes.
* **Super Admin Access**: Ability to configure system settings and manage users.

For more Info: Click Below

{% content-ref url="/pages/J1SQCPTRVCcODVTICZsy" %}
[Roles and Permission](/docs-for-ledsak/getting-started/roles-and-permission.md)
{% endcontent-ref %}