diff --git a/v3/docs/post-authentication/dashboard/tenant-management.mdx b/v3/docs/post-authentication/dashboard/tenant-management.mdx
index 5b81a9405..7c6a36343 100644
--- a/v3/docs/post-authentication/dashboard/tenant-management.mdx
+++ b/v3/docs/post-authentication/dashboard/tenant-management.mdx
@@ -51,6 +51,7 @@ Appropriate recipes must be active to turn on the login methods. For example,
 
 - to turn on `emailpassword`, initialize the EmailPassword recipe in the backend.
 - to turn on `OTP Phone`, initialize the Passwordless recipe with `flowType` `USER_INPUT_CODE` and contactMethod `PHONE`
+- to turn on `WebAuthn`, initialize the WebAuthn recipe in the backend.
 
 :::info
 
@@ -70,6 +71,7 @@ Also, initialize appropriate recipes in the backend SDK to use a secondary facto
 
 - to turn on TOTP, initialize the TOTP recipe in the backend.
 - to turn on `OTP Phone`, initialize the Passwordless recipe with `flowType` `USER_INPUT_CODE` and contactMethod `PHONE`
+- to turn on `WebAuthn`, initialize the WebAuthn recipe in the backend.
 
 <img src="/img/dashboard/tenant-management/secondary-factors.png" alt="Secondary Factors"/>
 
diff --git a/v3/docs/post-authentication/dashboard/user-management.mdx b/v3/docs/post-authentication/dashboard/user-management.mdx
index 14df5fc62..3d2bc8ba8 100644
--- a/v3/docs/post-authentication/dashboard/user-management.mdx
+++ b/v3/docs/post-authentication/dashboard/user-management.mdx
@@ -52,6 +52,23 @@ Enable some features such as user metadata and email verification in your backen
 
 ---
 
+## Manage WebAuthn devices
+
+When WebAuthn is enabled for your application, you can view and manage a user's registered WebAuthn devices through the dashboard. This includes viewing device details and removing devices if needed.
+
+To manage WebAuthn devices:
+
+1. Select a user from the dashboard
+2. Navigate to the "WebAuthn Devices" section
+3. View the list of registered devices
+4. Click the remove icon next to a device to remove it from the user's account
+
+:::info Note
+Removing a WebAuthn device means the user won't be able to use that device for authentication anymore. They will need to register the device again to use it for authentication.
+:::
+
+---
+
 ## Create user roles and permissions
 
 :::caution no-title