The application was developed with Core in a separate module, the wrappers are for service actions and the tables are read-only.

The same wrappers do the necessary checks against the user who is calling them (both by role and by the user identifier).

The application has the ability to scale for task sharing, and it is necessary to adapt the wrappers.

The application works with the role registered, allowing each consumer to adapt to the scenario that suits them.

Note: in the Save action of the task details JavaScript is being injected to add and remove CSS classes to the task selection ButtonGroup, in the "Required field" scenario, since it does not work if the same classes are not related with your buttons.