Features Provided
How to Exclude Users from the WordPress Activity Log
Not every trusted action needs to fill your audit trail. Logify's Exclusions settings let you stop specific users, roles, IP addresses, event types, post types, or post statuses from ever being recorded — the excluded activity is dropped before it is written to the database, so it never clutters the log.
What Are Exclusion Rules?
Exclusion rules tell Logify which activity to ignore. Since version 1.6.2, matching events are filtered out before they reach the database, so excluded activity is never stored, never counted, and never appears in the log or in exports.
How to Set Exclusion Rules
Go to:
Logify → Settings → Exclusions

Then set any of the rules below. Leave a field empty to exclude nothing for that rule.
| Rule | How to set it | What it excludes |
|---|---|---|
| Excluded User IDs | Comma-separated list of user IDs | All activity from those users |
| Excluded User Roles | Tick the roles to ignore | All activity from users in those roles |
| Excluded IP Addresses | One entry per line — exact address, wildcard, or prefix | Activity from matching IP addresses |
| Excluded Event Types | Tick the event types to ignore | Whole categories such as post, comment, or plugin |
| Excluded Post Types | Tick the post types to ignore | Activity on those post types |
| Excluded Post Statuses | Tick the statuses to ignore | Activity on posts in those statuses |

Exclude Specific Users
Enter one or more user IDs in Excluded User IDs as a comma-separated list. This is useful when one person makes frequent routine changes you never need to review.
Exclude User Roles
Tick any role under Excluded User Roles to ignore everyone in that role — for example, trusted administrators or editors doing daily work.
Exclude IP Addresses
Add addresses to Excluded IP Addresses, one per line. Three formats are supported:
- Exact —
203.0.113.10 - Wildcard —
192.168.1.*matches the whole range - Prefix —
10.0.matches any address starting with those octets
This is ideal for a fixed office network, a home office, or a development machine.
Exclude Event Types, Post Types, and Post Statuses
Use Excluded Event Types to drop whole categories of activity (such as comment or option), Excluded Post Types to ignore activity on specific post types, and Excluded Post Statuses to skip statuses such as auto-draft or inherit. These are useful for keeping routine autosaves and system-generated actions out of the log.
Why Use Exclusion Rules?
Exclusions keep the log focused on activity that matters:
- Less clutter from trusted, repetitive actions
- Faster reviews and easier auditing
- Smaller log tables and lighter exports
Because excluded events are never written, exclusions also reduce database growth — a stronger privacy control than deleting entries after the fact.
What to Be Careful About
Do not exclude too much. If you hide too many actions, you may miss something important later, and there is no record to fall back on because the activity was never stored. Exclude only clearly trusted activity you are confident you never need to review.
Conclusion
Exclusion rules let you shape a clean, meaningful activity log by ignoring trusted users, roles, IP addresses, and activity types before they are ever recorded. Set your rules, watch the log for a few days to confirm nothing important is being dropped, and adjust as needed. To manage history that is already stored, see How Can I Delete Multiple Activity Logs At Once? and Data Privacy, Anonymisation and Log Retention.
FAQs
How do I stop Logify from logging a specific user?
Go to Logify → Settings → Exclusions and add the user's ID to Excluded User IDs as a comma-separated list. From then on, all activity from that user is dropped before it is written to the log. To exclude a whole group of people instead, tick their role under Excluded User Roles.
Can I exclude an entire IP address range?
Yes. In Excluded IP Addresses, add entries one per line using an exact address (203.0.113.10), a wildcard for a full range (192.168.1.*), or a prefix (10.0.) that matches any address beginning with those octets. This makes it easy to exclude a whole office or home network.
Do exclusion rules delete existing log entries?
No. Exclusion rules only affect future activity — matching events are never recorded from the moment you save the rule. Entries logged before you set the rule remain in the database. To remove those, use the Delete Selected bulk action. See How Can I Delete Multiple Activity Logs At Once?.
Are excluded events stored anywhere?
No. Since version 1.6.2, excluded activity is filtered out before it is written to the database, so it is never stored, counted, or exported. This is why exclusions are the strongest way to keep sensitive or routine activity out of the log entirely — there is no hidden copy to clean up later.
Can I exclude certain post types or autosaves?
Yes. Use Excluded Post Types to ignore activity on specific post types, and Excluded Post Statuses to skip statuses such as auto-draft or inherit. Both are standard options on the Exclusions tab and are useful for keeping routine autosaves and system-generated changes out of the log.