Ability to manage inherited security for custom K2 roles

Background

Currently, the inherited security for custom K2 roles is Everyone with Modify and Delete rights. There is no way to modify the default, inherited security to add other users or modify/remove Everyone rights.

In order to customize the security for custom K2 roles, you need to break inheritance. If you have a lot of custom K2 roles, you need to go into each role individually. When adding a new custom K2 role, you need to remember to go into the role security and modify it accordingly.

Examples

Other areas in K2 have the ability to manage the inherited security which will then trickle down into the sub-locations under it:

• In K2 Designer, the "All Items" location. Security set here is inherited down into all folders (unless you break inheritance).

• In K2 Management, the Service Instances Security. Security set here is inherited down into all the instances (unless you break inheritance).

Proposed Enhancement

Adding the ability to modify the inherited security for custom K2 roles would save clients time. The current default, inherited K2 role security is not applicable to all clients and adds additional steps to development and maintenance.

This feature would bring K2 role security in line with other security areas within K2 that already have this functionality.