Row-level (and column-level) security

Currently, you can incorporate your security mapping in a project or publish a project as a computed asset.

In governed enterprise setups, there are cases (default in our Controlling department) that they prepare global data sources, but an entitlement table controls who can access which rows and columns.

It would be beneficial to have a configurable security layer for EasyMorph Server that controls via user roles/groups who can access which values based on field/dimension. Data assets (content) and also static dset-Files will be checked.

This would also affect actions (issues and item commands) as it might depend on the user's membership (group/role) if the action is available/supported or not.

In some cases, it might be helpful to mask data instead of completely hiding it (credit card number)