From 5aff5e76c1c3e01901f0287809154735bd0f8746 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Wed, 13 Aug 2025 09:27:27 -0500
Subject: [PATCH] Running Fleet locally: Building MDM features (#31829)

---
 docs/Contributing/getting-started/building-fleet.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/Contributing/getting-started/building-fleet.md b/docs/Contributing/getting-started/building-fleet.md
index ae926f9f2a..e77ccf8128 100644
--- a/docs/Contributing/getting-started/building-fleet.md
+++ b/docs/Contributing/getting-started/building-fleet.md
@@ -180,6 +180,8 @@ To start the Fleet server backed by the Docker development infrastructure, run t
 ./build/fleet serve --dev
 ```
 
+> To develop Fleet's MDM features, you have to pass a `--fleet_server_private_key` in your `fleet serve --dev` command. Learn how to generate a private key in [Fleet's server configuration documentation](https://fleetdm.com/docs/configuration/fleet-server-configuration#server-private-key).
+
 ### Developing the Fleet UI
 
 When the Fleet server is running, the Fleet UI is accessible by default at