diff --git a/docs/docs/.vitepress/sidebar.ts b/docs/docs/.vitepress/sidebar.ts
index d6547e810..74615621e 100644
--- a/docs/docs/.vitepress/sidebar.ts
+++ b/docs/docs/.vitepress/sidebar.ts
@@ -89,6 +89,15 @@ export const sidebar = [
                     },
                 ],
             },
+            {
+                text: "FAQ",
+                items: [
+                    {
+                        text: "Verification code",
+                        link: "/self-hosting/faq/otp",
+                    },
+                ],
+            },
             {
                 text: "Troubleshooting",
                 items: [
diff --git a/docs/docs/self-hosting/faq/otp.md b/docs/docs/self-hosting/faq/otp.md
new file mode 100644
index 000000000..8cdbb169e
--- /dev/null
+++ b/docs/docs/self-hosting/faq/otp.md
@@ -0,0 +1,19 @@
+---
+title: Verification code
+description: Getting the OTP for a self host Ente
+---
+
+# Verification code
+
+The self-hosted Ente by default does not send out emails, so you can pick the
+verification code by:
+
+* Getting it from the server logs, or
+
+* Reading it from the DB (otts table)
+
+You can also set pre-defined hardcoded OTTs for certain users when running
+locally by creating a `museum.yaml` and adding the `internal.hardcoded-ott`
+configuration setting to it. See
+[local.yaml](https://github.com/ente-io/ente/blob/main/server/configurations/local.yaml)
+in the server source code for details about how to define this.