diff --git a/doc/admin-guide/files/ip_allow.yaml.en.rst b/doc/admin-guide/files/ip_allow.yaml.en.rst
index 4c4553cb112..1f1843e21ac 100644
--- a/doc/admin-guide/files/ip_allow.yaml.en.rst
+++ b/doc/admin-guide/files/ip_allow.yaml.en.rst
@@ -14,6 +14,8 @@
 .. include:: ../../common.defs
 .. highlight:: yaml
 
+.. _ip-allow:
+
 ===============
 ip_allow.yaml
 ===============
diff --git a/doc/admin-guide/files/remap.config.en.rst b/doc/admin-guide/files/remap.config.en.rst
index ddf6a266f62..f1482aba0e0 100644
--- a/doc/admin-guide/files/remap.config.en.rst
+++ b/doc/admin-guide/files/remap.config.en.rst
@@ -496,6 +496,21 @@ mapping rules. (It is activated before any mappings and is never
 deactivated.) The filter `local_only` will only be applied to the
 second mapping.
 
+Implict IPAllow filter
+======================
+
+To allow control of :ref:`IP Allow<ip-allow>` it is treated as an implicitly active and named
+filter. When this filter is active IP Allow checks are done before remap. To prevent this for
+specific remap rules, this filter, named "ip_allow", must be disabled. The common way of doing this
+would be ::
+
+   .deactivatefilter ip_allow
+   map ...
+   map ...
+   .activateefilter ip_allow
+
+Note this entirely disables IP Allow checks for those remap rules.
+
 NextHop Selection Strategies
 ============================