Role-Based Access Control (RBAC) System

Description

Implement a granular Role-Based Access Control (RBAC) system for team and enterprise collaboration. This system will be built upon the Action System to control permissions for all operations.

Implementation Steps

1. Design and implement database tables for roles, permissions, and user_groups.
2. Integrate a permission check into the ActionManager::dispatch flow that runs before an action is executed.
3. Develop logic for defining standard roles (e.g., Viewer, Contributor, Manager) and assigning them to users for specific libraries or locations.
4. Implement APIs for managing roles and permissions.

Acceptance Criteria

• A Viewer can read data but cannot execute write actions (e.g., FileCopy, FileDelete).
• A Contributor can execute write actions but cannot manage library settings or permissions.
• An administrator can define custom roles with specific permissions.