developed and maintained by
and community
Copy a saved filter to the people who need it.
Zabbix filters are private to whoever created them. When one person builds the filter the whole team should be looking at, the rest have to recreate it by hand - or work without it.
Features · Examples · Install · FREE vs PRO · Portal · Docs
A good filter is knowledge: which hosts matter, which severities are noise, what the on-call person should see first. Zabbix keeps that knowledge locked to the account that saved it. User Filter Manager copies a filter from one user to any number of users or user groups, so the view an experienced engineer built becomes the view the whole team starts from.
|
Team defaults Build the filter once, push it to the group, and everyone opens Zabbix on the same picture. |
Onboarding A new colleague starts with the filters the team actually uses instead of an empty Problems page. |
|
Handover Someone leaves or changes role - their filters move to whoever takes the work on. |
Shift views Give the night shift its own set of saved filters without anyone rebuilding them. |
 Form - Select a source user and saved filter, choose destination users or groups, then copy and run the assignment from one dialog. |
One page under Administration. Choose the source user, pick which of their saved filters to copy, choose the destination users or user groups, and either save the transfer or save and run it at once.
Existing filters decides what a run does when a destination user already has saved filters:
- Add alongside - the default, and what previous versions always did: the copied filters are appended and the user's own stay untouched.
- Overwrite - the destination's saved filters of the copied kind (Problems, Hosts, Latest data) are replaced by the source set.
- Skip existing - only the filters the user does not already have are copied, matched by filter name within the same section.
The list shows a Last run column for every assignment: the time of the last run followed by (updated: N) - how many users' filters actually changed - or (no changes) when a rerun found nothing to do. An assignment that has never run reads Never.
FREE ships as GPG-signed deb / rpm packages from the initMAX repository - apt / dnf installs them and keeps them updated.
Open the product page, pick your OS and edition, and copy the ready-made command. FREE is fully public (no login); PRO fills in your token once you sign in. There's a feedback box right there too.
→ Open the installer on the Portal
Prefer a plain archive? Every release also ships as a ZIP straight from the repo - handy for offline or manual installs.
The module is enabled automatically during the package installation - verify it in Administration → General → Modules. Done.
There is no paid edition - everything below is in the one package.
| Feature | FREE |
|---|---|
| Sharing saved filters | ✅ |
| Centralized management | ✅ |
| Support for key Zabbix sections | ✅ |
| User-to-group synchronization | ✅ |
| Existing filters policy - Add alongside / Overwrite / Skip existing | ✅ |
| Last run overview per assignment | ✅ |
| Localised into all 25 Zabbix display languages | ✅ |
| High availability ready | ✅ |
| Licence | AGPLv3 |
| Zabbix | 6.0 · 6.2 · 6.4 · 7.0 · 7.2 · 7.4 - one package covers all |
| PHP | 7.4 or newer |
| OS | Debian/Ubuntu · RHEL/Rocky/Alma/Oracle/Amazon · SUSE |
| Editions | FREE (public repo) - there is no paid edition |
| Languages | All 25 Zabbix display languages - the module follows each user's own language setting |
| High availability | Ready. The filters live in the Zabbix database, not on the frontend node; install it on every node of an HA cluster and any node can serve it |
Every capability above works on every supported version - the same page, the same fields, the same labels, in the same order.
One package carries two module trees, because Zabbix accepts a manifest_version 1 module only below 6.4 and a manifest_version 2 one only from 6.4 up. The installer picks the right one for the frontend it finds, and picks again if that frontend is later upgraded across the boundary.
Two cosmetic differences come from the older frontends themselves and cannot be fixed from a module:
- Zabbix 6.0 draws no "?" help icon on the page header -
setDocUrl()arrived in 6.2. The documentation link in this README is the same one it would open. - Zabbix 6.0 and 6.2 keep user administration inside Administration, not in a top-level Users section, so the menu entry sits under Administration → User filter manager there, directly after Users.
- Documentation / Wiki
- Product page
- Portal - downloads, tokens, support tickets
- Source code (FREE, AGPLv3) - included in every package and published as a source archive on repo.initmax.com
- [email protected]