We have moved to GitHub Issues
Created by Arnold Visser 19 Jun 2017, 07:34:55 Updated by Sebastiaan Janssen 24 Oct 2017, 13:25:24
Is duplicated by: U4-10583
The 7.7 update kan be used to assign permissions to the folders in the Settings section, and make only some available to content-editors?
The new content-templates in 7.7 are awesome, but currently stored in the 'Settings' section. Editor/Content users can create them, but not edit them, unless they get full access to the settings section.
Since we already have this issue with the availability of the dictionary to customers, it should not be an afterthought when implementing the content-templates. Also if done via User permissions, the dictionary can also finally properly available for content editors.
I agree, for my customers the Dictionary being under settings also is somewhat difficult, same would go for blueprints.
There's been talk about an "editor" settings and "power user" settings separation. Something will come, but possibly not until v8. Anyway, this is hearsay and speculation. I'm sure someone from HQ will clarify. Glad you like the blueprint thing. :)
@lars-erik Shame that it will take some time, because this will limit the blueprint functionality from the start. I might create a package that adds it to a custom section will be the best option for now. Unless HQ comes up with something better. Extending permissions to the settings section would already fix most use cases.
This was done because we needed a Minimum Viable Product
The options are:
The tree's permissions are not authorized by the 'settings' section , they are authorized by the content section which means if you have access to content you can still navigate to the blueprint editor. So.... this means you could create a dashboard and/or submit a PR for that functionality.
In the meantime, feel free to dream up the correct scenario and let us know :) we can move things around after release.
Moving dictionary to translations has bee discussed before: http://issues.umbraco.org/issue/U4-6620 I've asked to see if that is something we can do for 7.7 or maybe we can make this other 'editor' tree or something.
Type: Usability Problem
Backwards Compatible: True
Affected versions: 7.7.0
Due in version: