admin-roles-crud

Role-based access control management is handled by creating, editing, and deleting roles for user and organization access. The skill provides a hardcoded permission catalog grouped by namespace with explicit naming conventions for precise authorization.

Role assignment is managed through integration with the admin-user-crud dependency, which coordinates user role assignments. The skill handles role definitions while admin-user-crud applies those roles directly to individual user records.

Permission checking consumes the otp-auth dependency to validate authorization for admin interface actions. The skill defines explicit and implicit permissions for system roles, then otp-auth verifies that a user holds the required permissions before granting access.

Explicit permissions are individually named entries from the hardcoded catalog grouped by namespace, while implicit permissions are automatically granted to system roles. System role handling ensures seamless functionality by managing these implicit permission sets without manual configuration.

Yes, both otp-auth and admin-user-crud are required dependencies. The skill consumes otp-auth for permission checks during authorization and integrates with admin-user-crud to coordinate the assignment of managed roles to users in the admin interface.

The permission catalog is hardcoded with groupings by namespace and explicit permission naming conventions. This fixed structure ensures consistent role definitions across the admin interface but does not support dynamic permission creation at runtime.