Umbraco-cms: V8: Spec out - limiting editorial access by language

[kjac]

We need to create sub tasks for this feature which is what this task is.

Here's the gist:

Since languages are a first class citizen in V8, wouldn't it make sense to limit the editorial access to language specific content?

Specifically I'm thinking that the users should always be able to see content in all languages, but only edit the languages permitted by their user groups. The config would be something like this:

I have a crude but functional PoC that only allows users to edit the variation properties in the permitted variant languages. I'd be happy to work some more on it, if this is indeed a feature worth working on.

[dawoe]

Hi @kjac

Thanks for raising this issue. I think it would be a good addition personally. We now often have seperate trees for languages and give editors rights to only one tree...so we have editors per language.

I will label this as needing HQ input.

Dave Community Pull Request team

[kjac]

@dawoe exactly!

I think it'd be a killer feature and also possibly a decisive factor when comparing Umbraco with other CMS'es for a new project.

Considering how little change is actually needed to get the PoC up and running, it's definitively worth chasing after in my opinion.

[nul800sebastiaan]

Thanks @kjac - we recognize the need for this as well. Currently this is not on the roadmap while we wait for when people start using the variants feature and we get some more feedback on it.
Our permissions model is quite complex already and we're still thinking about the best way to implement this feature.

[kjac]

@nul800sebastiaan cool. Let me know if I can do anything to help.

If we're to fully leverage the power of language variants, I am certain a need for this feature will arise pretty quickly for larger international sites with multiple editors around the globe. I'd really hate to see the lack of this feature as the cause for choosing another CMS over Umbraco.

[MatsStam]

This is most def something that should be added in my opinion. Handling large multilingual sites is impossible without it :/

[sbesteman]

Since languages are a first class citizen in V8, wouldn't it make sense to limit the editorial access to language specific content?

Specifically I'm thinking that the users should always be able to see content in all languages, but only edit the languages permitted by their user groups. The config would be something like this:

I have a crude but functional PoC that only allows users to edit the variation properties in the permitted variant languages. I'd be happy to work some more on it, if this is indeed a feature worth working on.

This is a must have for our project with a lot of language variants. When will it be included? Or has someome build it already and can it be packaged?

[FransdeJong]

Ran in to this issue just now. This is really a must have when working with different editors for different languages.

[rasmusbollerup]

Please make this happen. Missing this feature is a show stopper on current client projects that won't happen without it.
To quote Kenn: "If we're to fully leverage the power of language variants, I am certain a need for this feature will arise pretty quickly for larger international sites with multiple editors around the globe. I'd really hate to see the lack of this feature as the cause for choosing another CMS over Umbraco." And this is exactly what's about to happen.

[henrikgm]

I totally agree that this feature is badly needed

[Ladefuss]

Completely agree. Hard to fully utilise languagevariants without it.

[FransdeJong]

@nul800sebastiaan Is there any update from HQ if they are interested in this feature and if it is on a roadmap?

[nul800sebastiaan]

We are interested but it is not on the roadmap, we have yet to think about how to implement it and are currently not able to invest the proper time into it.

Right now, the recommendation is to use the older way of doing multilingual websites by using multiple nodes in the root of your tree (/en, /nl, fr) and giving editors access to their own language trees.

[rasmusbollerup]

@nul800sebastiaan I realize this is not the place for lengthy discussions, but that is very bad news as this will totally undermine the whole argument that Umbraco 8 is now an enterprice level CMS.

The language variant setup on any site is part of the core architecture/configuration and doing it the old way will have the site stuck with that architecture "foreverthereafter". You would really do the community a favor by taking this feature into the roadmap. @kjac already made an excellent UI for the feature:-) eom

[kjac]

@rasmusbollerup if I'm not mistaken you can achieve most of this using the existing extension options for the back office, maybe with one or two caveats.

[nul800sebastiaan]

I do understand the disappointment and I wish I could help. Unfortunately we have limited resources and we're currently have our hands full with all of the other things that are on the roadmap: https://umbraco.com/products/roadmap/

[nul800sebastiaan]

That said, I'll make sure to share the feedback at HQ, in case some of my colleagues have more to add to this feature request. 👍

[arknu]

@nul800sebastiaan Could we at least put this on the roadmap, even if it is under Later? Maybe get an RFC going to iron out the details...

I'll join the chorus saying this is an essential feature for large multilingual sites.

[nul800sebastiaan]

For a bit of background information: In the past we've been very good at over-promising and under-delivering.

Therefore, everything on the roadmap is something we've committed to working on and we have enough detail/insight into how the feature needs to work.

At this moment we don't have a good insight in how we think it could/should work and we can not commit to working on it in the future, this is why this feature is not (yet?) on the roadmap.

As always, we're listening and will incorporate all your feedback on this issue in the final implementation once we can commit to get to it, so anything you can add here is great.

I agree that this probably requires an RFC, but an RFC also requires someone from HQ to be able to guide and complete it, I don't think we have available resources for that at the moment.

[mzajkowski]

Hey there! @Shazwazza - is there anything happening around it maybe? We welcomed a new v8 project and literally just stopped because of the ^^. Curious if it's considered as something possible to worked on "next" or now something totally out of the scope / planning / ideas? Please let me know.

[Shazwazza]

Hey mate, we are working on planning this now - meaning figuring out how exactly this should work, identifying the various 'gotchas', defining MVPs, etc. So we'll be able to provide some implementation details once that's ready

[shearer3000]

hello - we too have this requirement in umbraco 8 projects. Is it possible for the community to vote on having items like this prioritized on the roadmap? thx

[shearer3000]

hi - has there been any progress on this (for 8.7 maybe)? thanks

[picadu]

Hey mate, we are working on planning this now - meaning figuring out how exactly this should work, identifying the various 'gotchas', defining MVPs, etc. So we'll be able to provide some implementation details once that's ready

Any updates here?
That's a key feature for multinational websites.
thanks

[juliangrahame]

Yep. Defo a must-have for larger corporate sites. Otherwise it's U7 :(

[nul800sebastiaan]

Unfortunately many other priorities came up so this has been on the backburner for a while (we don't have a timeline for when we'll get back to it).

Otherwise it's U7 :(

I am not sure how v7 would be different, it is still entirely possible to build a site exactly like in v7 with separate content roots for each language.

[FransdeJong]

I think he means, otherwise you'll have to use V8 like V7 and loose the language benefits.

Hopefully this issue will get on the planning soon. It's hard to tell customers that we use a CMS that is multilingual in core but we can't manage who can edit the different languages.

Another option could be to make it a community driven update by starting a Request For Comments? That way the community can be guided to create this update?

[icavalheiro]

Any news on this feature? This gonna be a game changer for my company, allowing us to migrate some projects from Drupal to Umbraco.

[JeffreyPerplex]

This sounds like an excellent idea!