Hi again,

I need to enable some members (not "Moderators" or J! admins) to edit profiles of certain other members.

Wannabe-editor and to-be-edited have in common:
- CB Connection (exclusively, means they're only connected with each other, no one else - both ways)
- A CB field with the same hashed value unique for these connected members.

Not in common = differences in between editor and edited:
- Usergroups
- ACL
- Values of other CB fields (e.g. in one CB field editors have a value of 1, while edited have a value of 0)

Editors shall be able to edit the profiles of their connections, but not vice versa. (I know, that won't be a biggie once the basic concept is working.)

How?
Been thinking to - per Auto Action and when matching conditions - temporarily give an editor a "Moderator" usergroup while they're accessing a connected profile (and remove it again once they're done), but that seems a bit risky.
Any better way I can't think of - without hacking core?

Thanks!

Thanks, understood.

I do have that structure already for different reasons. Though not one "team set" per editor/edited group, but that's not the issue as I can prevent further "cross-group" editing with conditionals.

But, as confirmed by you, I must then make the editors full "CB Moderators" and, if I understand it right, that's a no-no due to the other moderator permissions they would inherit. As I already said in my initial post, "that seems a bit risky".

Too bad... guess I'll need to look into modding the core

Hi Kyle,

Just FYI, I found a solution without messing with the core.

In short, I've created a new tab restricted to the editors' ACL and, with the help of a new Custom HTML field, placed a form in there, with which the relevant fields can be edited while viewing the connected profile.

Done and dusted.