U4-10030 - Make editing content-templates available to content-editors in 7.7?

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.

Comments

Danny Drogt 19 Jun 2017, 07:43:18

I agree, for my customers the Dictionary being under settings also is somewhat difficult, same would go for blueprints.


Lars-Erik Aabech 19 Jun 2017, 09:22:30

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. :)


Arnold Visser 19 Jun 2017, 09:33:06

@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.


Shannon Deminick 21 Aug 2017, 06:18:31

This was done because we needed a Minimum Viable Product

The options are:

  • Create a dashboard to edit them - we didn't have time and not sure if yet another dashboard is a good idea
  • Modify the dialog to also edit - not very UX friendly but might be possible and work well if implemented in a clever way
  • Make the content section have 2 trees - this means a bit of a change in UX (moving cheese) and at this point in time I think i recall the content section having some issue with more than one tree but that would need testing/investigation
  • Put the tree in settings - this was quick and easy so that's what was done for now

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.


Priority: Normal

Type: Usability Problem

State: Submitted

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.7.0

Due in version:

Sprint:

Story Points:

Cycle: