Andy Whalen

Creates a log file for network/multisite super admin actions.
The following actions are logged for Super Admin users. WordPress action names are listed in parenthesis:
<ul>
<li>change network settings (update_site_option)</li>
<li>grant super admin privileges (granted_super_admin)</li>
<li>revoke super admin privileges (revoked_super_admin)</li>
<li>upgrade blog (wpmu_upgrade_site)</li>
<li>add blog (wpmu_new_blog)</li>
<li>set blog archived (archive_blog/unarchive_blog)</li>
<li>set blog deleted (make_delete_blog/make_undelete_blog)</li>
<li>set blog mature (mature_blog/unmature_blog)</li>
<li>set blog spam (make_spam_blog/make_ham_blog)</li>
<li>delete blog (delete_blog)</li>
<li>delete user (wpmu_delete_user)</li>
<li>delete user (deleted_user)</li>
<li>change other user’s settings (edit_user_profile_update) [NOTE: doesn’t show diff]</li>
<li>change blog setting (updated_option) [NOTE: may occasionally log annoyingly large diffs]</li>
</ul>
The following actions are logged for ANY user:
<ul>
<li>login (wp_login)</li>
<li>logout (wp_logout)</li>
<li>new user (user_register)</li>
</ul>
Some actions that change data will show what the value was before and after.
Below is an example of a log entry when the user ‘smith’ has changed the Network site name from “WP Local Network” to “WP Local Networks”:
<pre><code>[Tue, 03 Sep 2013 13:45:49 +0000] [smith:1] [update_site_option] [1] [site_name] [(WP Local Network)->(WP Local Networks)] [127.0.0.1] </code></pre>
Each line in the log file will roughly follow the below example. Individual actions may log slightly different information, but the DATETIME, USERNAME, USER_ID, ACTION, and IP_ADDRESS sections should always be populated.
<pre><code>[DATETIME] [USERNAME:USER_ID] [ACTION] [AFFECTED_OBJECT_ID] [DATA_TITLE_OR_KEY] [(VALUE_BEFORE)->(VALUE_AFTER)] [IP_ADDRESS] </code></pre>

Observer

Creates a log file for network/multisite super admin actions.

chexwarrior

This plugin allows administrators to enable or disable other user account’s logins.
When a user is disabled: 
* They can not login to the site 
* They are immediately logged out of the site 
* Any <a href="https://make.wordpress.org/core/2020/11/05/application-passwords-integration-guide/" rel="nofollow ugc">application passwords</a> created with this user will no longer authenticate with the WP REST API
<h4>WP-CLI Integration</h4>
This plugin integrates with WP-CLI and provides the following two commands:
<pre><code># Enables the target users
wp user enable <List of User IDs, Logins or Emails> [--all]

# Disables the target users
wp user disable <List of User IDs, Logins or Emails> [--all]
</code></pre>
<h3>Support</h3>
This plugin is developed on the author’s own time so there is no guarantee that reported bugs will be fixed in a timely fashion.
To report a bug please visit the plugin’s <a href="https://github.com/ChexWarrior/wp-user-disable-login" rel="nofollow ugc">GitHub repository</a>.

User Login Disable


As per the author's FAQ, I just wanted a plugin that disabled users easily without any extra bells and whistles. Extra points for the WP-CLI integration!


Does what it says on the tin

Allows administrators to disable other user logins.

Observer vs User Login Disable