AAM is tightly coupled with WordPress core and puts extra focus on user authentication and authorization. In the end of the day there are only two type of users that interact with a WordPress website – visitors and authenticated users (those who confirmed their identity either with username/password pair, through single-sign-on or JWT token).
WordPress core and default WordPress dashboard already does great job managing list of users and grouping them together by roles (or multiple-roles per user). AAM enhances WordPress core with several very useful features that you can utilize on the AAM page.
Note! The screenshot above is from AAM v5.9.2. I do not exclude the possibility that by the time you read this article AAM UI may look slightly different however all the mentioned features in this article will be still available to use.
When you go to the AAM page, you’ll notice Users/Roles Manage panel that contains the list of all users on the Users tab. The list has pagination with 10 users per page however for your convenience you can either search for a very specific user by the name or filter out the list by the role. The second filter option is quite useful when you quickly need to go through the list of users that belong to the same role.
Note! AAM automatically determines based on User Level and several custom capabilities if current user has ability to manage users or perform specific actions on each user.
AAM itself does not create new or delete existing users. That is why when you click on the Add New button, it’ll forward you to the default WordPress Add New User page. AAM also does not give you an option to delete any user from its UI. That is something you can do by going directly to the user’s profile page or from the Users->All Users page.
So let’s quickly go through the list of all the options that are available to manage access to the WordPress website for an individual user.
Manage Access On User Level . This option literally reloads the Main Panel with the list of all features that current users can use to define access to the website resources for a particular user. 99% of the time you probably will use this option when you need to define more granular access for the user.
FYI! It is strongly encouraged to manage access to your website resources on role level and let users to inherit access settings from the parent role(s). With the large number of users it is very easy to loose track of all the changes that have been made on each individual user.
Block User . This is quite a powerful way to suspend user account for an indefinite time. WordPress does not really have the concept of the user status and all user records are active unless completely deleted from the database. AAM allows blocking any user without actually deleting the account. This feature can be quite useful to keep data integrity especially when you keep user activity logs for audit purposes.
FYI! If a webmaster blocks user account that already is logged in, AAM will automatically logs that account out.
Edit User’s Account . This option has been enhanced in the past few AAM releases and allows you to define temporary access to the website for any user. You can define up to a minute for how long any individual user will have access to the account as well as what action needs to be performed when access expires. For more information about this feature, please refer to the How to create temporary WordPress user account article.