Named permissions keys that store predefined permissions for projects/groups/users

[Nicklas Nordborg]

This is an idea that suddenly popped up... If it works it would solve #1187 and #1236 and make it easier to share multiple items to a predefined set of users, groups and projects.

The idea is to introduce a "Named permission key" item. This item is shareable and acts as a placeholder for defining permissions. A batch importer could then, for example, include a column that holds the name of a permission key and apply the same permissions to the created item.

Permissions keys are personal and once applied the connection to the key is lost, meaning that if the permissions in the key are modified it doesn't affect items that was shared using the key as a template.

There are several use cases that can benefit from this:

• Batch importers can reference a permission key and assign permissions to new items, and maybe also update permissions on existing item (the remaining problem is if the existing permissions should simply be replaced or if they should be merged).
• The manual share dialog can use the permissions keys to quickly assign a lot of permissions.
• A project can be linked with a permission key and when the project is active the permissions in the key are applied to new items instead of just sharing to the current project.

[Jari Häkkinen]

Great, this would solve a few issues in our lab.

[Nicklas Nordborg]

(In [5368]) References #1459: Named permissions keys that store predefined permissions for projects/groups/users

Added data, core and test classes. Updated data-layer documentation. Implemented the third use case in the ticket description at the core level (A project can be linked with a permission key...).

[Nicklas Nordborg]

(In [5369]) References #1459: Named permissions keys that store predefined permissions for projects/groups/users

Should have been in the previous commit. Forgot to save the last changes in MagicDraw.

[Nicklas Nordborg]

(In [5370]) References #1459: Named permissions keys that store predefined permissions for projects/groups/users

Added gui pages for managing permission templates. It is now possible to assign a template to a project and to select templates when sharing items. Eg. item 2 and 3 in the list above have been fully implemented. I think I'll close this ticket now and implement the first item in #1187 or #1236.

[Nicklas Nordborg]

The batch importer use case will be solved as part of #1236.

[Nicklas Nordborg]

(In [5387]) References #1459: Named permissions keys that store predefined permissions for projects/groups/users

Incorrect mapping between permission template and projects.