Fully remove/hide content items in grid you can't edit

[nerdegutt]

With reference to this discuss thread, and ever growing XP popularity and reach, I see a need to simplify the content studio admin for users with limited privileges.

In a real life three site config having some 1000 users allowed to add i.e. blog posts on separate websites, it would really improve the content studio user experience if the users only saw the content they were allowed to edit. Today potential content creators are turned off by the massive amount of non applicable content and confused by needing to open paths that are dimmed to get to the content they actually are allowed to interact with.

Today there is no separation of public side roles (the role Everyone needs access to most everything) and admin side roles, meaning all the paths in the grid is visible (although greyed out) to all admin users.

My wish is for a feature to (at least by default) hide all paths not applicable to the logged in users. Preferably also presented with a github style path "concatenation", or "auto-traverse" in lack of a proper word, when you have access to content a few levels down the three:

/mysite/a/b/c/i-can-write-stuff-here
/mysite/blog

This could perhaps be visually toggled ux wise as a "Hide content I cannot edit"-checkbox at the bottom of the grid, or the opposite logic "Also show content I cannot edit" if you so prefer.

[sigdestad]

Hi Erlend! Sadly, this cannot be accomplished like you desire. i.e. hiding all content. The reason is that one has to be able to navigate items one cannot edit, and one even has to be allowed to link to content one cannot edit. That said, there is definetly room for simplifying things for the users. Here are our ideas on the topic:

• A site selection mode. Allowing the user to select what site he wants to work on in content studio
• Introducing the "tasks" we have talked about in another issue. So when the user clicks "new" tasks will guide him right. I.e. "New blog post" lets the user select site (if many) and then automatically creates the post in the /posts/ folder of the site.

What are your thoughts on this?