tab access for user only?

Since the new AJAX core plugin I try to let the user edit everything form front end.
However, is there a way to make a tab only visible to the user himself and moderator?

thank you

socialfan wrote: Since the new AJAX core plugin I try to let the user edit everything form front end.
However, is there a way to make a tab only visible to the user himself and moderator?

thank you

Privacy plugin.

from what I understand: the user (if enabled) gets the option to chose "invisble on profile" this will hide the tab to all users but him and mods - correct?

But I can not assign this privacy level from back-end to that level. The user MUST chose this by himself and is able to change that option any time - correct?

In my scenario, I dont want to display some information to any one but the user and admin (like contact information) but would like the user to edit his data from the front end only.

from what I understand: the user (if enabled) gets the option to chose "invisble on profile" this will hide the tab to all users but him and mods - correct?

Yes.

But I can not assign this privacy level from back-end to that level. The user MUST chose this by himself and is able to change that option any time - correct?

Correct.

In my scenario, I dont want to display some information to any one but the user and admin (like contact information) but would like the user to edit his data from the front end only.

This is a bit more complicated. You'd need to use delimiter fields, IF statements, and substitutions to render the fields instead of letting them render as normally. The IF statements would let you check if the user is viewing himself for example and only display its contents if that were the case. Please see tutorials within my signature for further substitution usage information.

do you think it would make sense to include this setup in future releases of the privacy plugin? Like "advanced privacy backend only".

From what I understand the funtion is already there but can not be enabled in be.

It'll be possible with CB 2.0, but with 1.x we're feature locked. I don't think there will be a new CB Privacy before CB 2.0 (it'll become a part of CBs core).