PermissionMap Model
Overview
The permissionmap table is designed to manage and store mappings between roles, permissions, and other access control attributes in an application. It enables the mapping of roles to specific permissions, allowing for dynamic and fine-grained access control based on roles and licenses.
Fields
| Field | Type | Description | Required |
|---|---|---|---|
| id | string | A unique identifier for the permission map | ❌ |
| rolesId | string | The identifier of the role associated with the permission map.This field links roles with their associated permissions. | ❌ |
| application_id | any | Identifies the application in which the role and permission are valid. In a multi-app environment, this enables role permissions to be scoped per application. | ❌ |
| license_role | any | Represents the license-level role that this permission applies to. It could be used for license-specific permissions or access restrictions(siteAdmin/Admin/Editor/Viewer/Guest). | ❌ |
| permisssionsId | string | The identifier of the permission linked to this map.This creates a direct link between a specific permission and a role. | ❌ |
| created_at | date | The timestamp when the permission map was created. Useful for auditing and tracking changes over time. | ❌ |
| modified_at | date | The timestamp when the permission map was last updated. | ❌ |
| type | string | The type or category of the permission map.Help in filtering or classifying permission maps. | ❌ |
Sample JSON
{
"id": "example_value",
"rolesId": "example_value",
"application_id": "example_value",
"license_role": "example_value",
"permisssionsId": "example_value",
"created_at": "example_value",
"modified_at": "example_value",
"type": "example_value"
}