Restrict access to single catalog items based on user rights

Hi,

I want to restrict access for single catalog items (f.ex. checkbox to "publish" an article, which triggers the display of an article in the frontend) to certain backend-user/backend-user-groups. They should only be available/visible to admins or reporters or whatever.

Does anybody have an idea how to do this?
Is there a hook available to extend user rights or can this be done by a module?
Every hint is highly appreciated.

Thanks a lot,
Sares

There is no user rights at the moment. The Alpha version will include FE groups for editability of the items.

You can however use the pages method to create a category tree and then restrict access to those pages, if they are not logged in.

Hi Thyon,

thank you very much for your answer.

FE restrictions and pages doesn't help in my case, because the reporters are logged in and have access to the backend resp. catalog and here the restrictions should take place. In general they should be able to edit catalog items, but in detail some of the catalog items should be "invisible" to them, depending on their user-rights/user-group.

It is comparable with a simple workflow management, where editors can create new content, but they can't publish it.
What do you think, would this be an interesting feature for 2.0? If so, maybe I should write a feature request...

Kind regards,
Sares

We already have something like that for the BE in the feature requests, but it won't make it into 2.0, maybe 2.1

Ok, thank you very much!

Kind regards,
Sares

I've just posted a feature request at code.google.com for that because I really need this feature as soon as possible. Thanks!

You can try to make something like that with dca.
It's now possible to make it like this ->
$GLOBALS['TL_DCA']['tabellenname']['fields']['spaltenname']['eval']['readonly'] = true;
the field spaltenname is now only readable... that is also working with grouprights (if group=1 than ...).

So try it out.. I hope this will do it for you ;-)

regards