diff --git a/website/docs/flow/executors/headless.md b/website/docs/flow/executors/headless.md
index 4fd4f1c6b..46b408389 100644
--- a/website/docs/flow/executors/headless.md
+++ b/website/docs/flow/executors/headless.md
@@ -8,4 +8,4 @@ The following stages are supported:
 
 -   [**identification**](../stages/identification/)
 -   [**password**](../stages/password/)
--   [**authenticator_validate**](../stages/authenticator_validate/) (currently only DUO devices are supported)
+-   [**authenticator_validate**](../stages/authenticator_validate/)
diff --git a/website/docs/providers/ldap/generic_setup.md b/website/docs/providers/ldap/generic_setup.md
index bd039b3b9..4c1fa24d0 100644
--- a/website/docs/providers/ldap/generic_setup.md
+++ b/website/docs/providers/ldap/generic_setup.md
@@ -11,7 +11,7 @@ title: Generic Setup
 2. Create a new group for LDAP searches. In this example `ldapsearch`. Add the `ldapservice` user to this new group.
 
 :::info
-Note: The `default-authentication-flow` validates MFA by default, and currently only Duo-based MFA devices are supported by LDAP. If you plan to use only dedicated service accounts to bind to LDAP, then you can use the default flow and skip the extra steps below and continue at [Create LDAP Provider](#create-ldap-provider)
+Note: The `default-authentication-flow` validates MFA by default, and currently everything but SMS-based devices are supported by LDAP. If you plan to use only dedicated service accounts to bind to LDAP, or don't use SMS-based authenticators, then you can use the default flow and skip the extra steps below and continue at [Create LDAP Provider](#create-ldap-provider)
 :::
 
 ### LDAP Flow
diff --git a/website/docs/providers/ldap/index.md b/website/docs/providers/ldap/index.md
index 2bb8b33f8..b9313979c 100644
--- a/website/docs/providers/ldap/index.md
+++ b/website/docs/providers/ldap/index.md
@@ -78,6 +78,10 @@ The following stages are supported:
 
     SMS-based authenticators are not supported as they require a code to be sent from authentik, which is not possible during the bind.
 
+-   [User Logout](../../flow/stages/user_logout.md)
+-   [User Login](../../flow/stages/user_login.md)
+-   [Deny](../../flow/stages/deny.md)
+
 #### Direct bind
 
 In this mode, the outpost will always execute the configured flow when a new bind request is received.