privacy_delete_me and privacy_disable_me not appearing in profile edit

krileon wrote: Sounds like you adjusted the Moderator View Access Level within CB > Configuration > Moderation and are causing everyone to have CB Moderator permissions or you added usergroups to whatever view access level you have selected.

Yes! You are right!
I've added 3 new groups and ACLs today, following this guide:
www.joomlapolis.com/documentation/18237-cb-auto-actions-assigning-usergroup-based-on-cb-field-value
What shoul I do to get it working normally?

Now I have next ACL:
User ---> Manager, Registered, Super Users, User
Applicant ----> Applicant, Manager, Registered, Super Users
and so on...

Ok, I've made them appear (delete me and disable me) by changing Moderators View Access Level from "Special" to "Super Users". With any other Access level it won't work (tested it).
Everything is good with the Update log as well right now.

With any other Access level it won't work (tested it).

Because likely the user you're editing is within the Special view access level. CB Moderators can not disable or delete themselves. Suggest checking your Special view access level and ensure the usergroups you want it to include are selected correctly.

krileon wrote:

With any other Access level it won't work (tested it).

Because likely the user you're editing is within the Special view access level. CB Moderators can not disable or delete themselves. Suggest checking your Special view access level and ensure the usergroups you want it to include are selected correctly.

Did not understand very well.... here are my access levels:
Here we see that the Special ALC has the Registered group in it - this is the element making trouble? I just need to delete Registered from Special and it would be the default setting?

Special Author, Manager, Registered, Super Users 3

That's why you were having this issue. Registered users are being given Special permission. I do not recommend doing this. You set Moderator View Access Level to special, which includes Registered users resulting in basically all registered using being CB Moderators. Changing Moderator View Access Level to Special Users of course fixes this, but I still do not recommend including Registered usergroup in such a high permission view access level.