How to approve Avatars and images

I am getting generated email that an image requires approval, but I have yet to find where I can do this with the latest version of CB. With Joomla 2.5 and earlier versions of CB, this was pretty easy, but since we have upgrade to Joomla 3.9 and CB 2.4, can't figure out how to find who uploaded the image and how to approve it. If I user the User Search tools and select Pending under Avatar, nothing comes up, but If I choose Approved in that drop down, all 4000 users come up.

Create a Joomla menu item with a menu type of Community Builder > Moderate Images or use the CB Workflows module to link to the image approval page. This is how it has always functioned.

That will work. Thanks.!!! I also discovered that when we did the update from 2.x to 3.x the avatarapproved column in the comprofiller table was not set correctly which is why when I went to search for these that needed approval in the work flow module, they did not come up. The menu item which i has assigned to our admins will make it easier for them to approve the images. A simple SQL statement in phpmyadmin got that column back to where it should be.

Updating should not have toggled images that were pending approval to approved. What do you mean by it wasn't set correctly?

In theory that is correct. The avatarapprove column defaults to a 1. When a user submits an image, that column is set to a 0. When the update occurred, it set every user column to a zero. I verified that from the date we did the update. This is why we have been having difficulty trying to figure out which images required approval. I have that all back to normal and with the few that we tried for testing purposes, it is now working correctly. When the moderator approves the image, it toggles that column back to a 1. Not the way I would have done it if I was designing the Database Structure. In the long run, we are now workign correctly again!!

It should not have touched that columns values on install. What version did you upgrade from? You said 2.x to 3.x, but 3.x doesn't exist. If you can provide exact versions will be able to review the changes between the versions to see if there's a potential cause. As is I'm seeing no such issues upgrading a test install from 2.0 to 2.4.