The problem is that I want to restrict a backoffice user to a specific part of the site. The easiest way to do this, is to select a "Start Node in Content" for the user.
However when selecting a start node, the user loses the Recycle Bin functionality.
I'd like to keep the restricted user access to the Recycle Bin..
Is there a way to do this?
Sorry, don't know of any way to do that. I can see why you might want this but I think it goes against the general idea of limited content access. You could always suggest it as a feature, however it might be a bigger can of worms than you might realize.
I see.. It would be very handy, i expected it to work.
Say you have multiple content editors, each handles it's own part in an organization. And they can't use the Recycle Bin. I think the Recycle Bin should show up, restricted according to user's Start node.
Well, thanks anyways, i'll try to submit this as a feature request.
Setting a Content start node for user removes the Recycle Bin for the user
The problem is that I want to restrict a backoffice user to a specific part of the site. The easiest way to do this, is to select a "Start Node in Content" for the user. However when selecting a start node, the user loses the Recycle Bin functionality. I'd like to keep the restricted user access to the Recycle Bin.. Is there a way to do this?
Thanks, Levente
Sorry, don't know of any way to do that. I can see why you might want this but I think it goes against the general idea of limited content access. You could always suggest it as a feature, however it might be a bigger can of worms than you might realize.
https://our.umbraco.org/contribute/report-an-issue-or-request-a-feature/
I see.. It would be very handy, i expected it to work. Say you have multiple content editors, each handles it's own part in an organization. And they can't use the Recycle Bin. I think the Recycle Bin should show up, restricted according to user's Start node. Well, thanks anyways, i'll try to submit this as a feature request.
There is already an issue on this and its a shame it has not been fixed.
Its really a multi-issue feature.
http://issues.umbraco.org/issue/U4-239
Lets vote it up!
is working on a reply...