id summary reporter owner description type status priority milestone component version resolution keywords cc 1459 Named permissions keys that store predefined permissions for projects/groups/users Nicklas Nordborg 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. " task closed major BASE 2.16 core fixed