diff --git a/docs/platforms/unity/troubleshooting/img/unity-file-system-access-permissions.png b/docs/platforms/unity/troubleshooting/img/unity-file-system-access-permissions.png
new file mode 100644
index 00000000000000..e3c351744baa8c
Binary files /dev/null and b/docs/platforms/unity/troubleshooting/img/unity-file-system-access-permissions.png differ
diff --git a/docs/platforms/unity/troubleshooting/known-limitations.mdx b/docs/platforms/unity/troubleshooting/known-limitations.mdx
index d0b9b63560eea7..e31e387b572ceb 100644
--- a/docs/platforms/unity/troubleshooting/known-limitations.mdx
+++ b/docs/platforms/unity/troubleshooting/known-limitations.mdx
@@ -4,6 +4,12 @@ sidebar_order: 9000
 description: "Learn more about the Unity SDK's known limitations. "
 ---
 
+## File System Access Permissions
+
+![A popup requesting permissions to read from the `Downloads` folder](./img/unity-file-system-access-permissions.png)
+
+Starting with macOS Mojave (10.14), directories like `Desktop`, `Documents`, and `Downloads` are considered privacy-sensitive locations and are protected by the operating system's security sandbox. When running a Unity application from one of these locations, users might encounter a popup requesting access. This occurs because the default .NET `HttpMessageHandler` attempts to resolve domain names, which requires filesystem access. Note, that disallowing access to these locations does not affect the SDK from reporting errors.
+
 ## Stack Traces
 
 ### Line Numbers Missing On Button Click Events