diff --git a/content/en/docs/refguide/modeling/import-and-export/_index.md b/content/en/docs/refguide/modeling/import-and-export/_index.md
index 28017871705..c021b5d8e10 100644
--- a/content/en/docs/refguide/modeling/import-and-export/_index.md
+++ b/content/en/docs/refguide/modeling/import-and-export/_index.md
@@ -35,6 +35,7 @@ Current undesired locations:
 * deployment/
 * nativemobile/builds/
 * vendorlib/temp/
+* mprcontents/
 {{% /alert %}}
 
 {{% alert color="warning" %}}
@@ -234,6 +235,22 @@ The app package is created and exported.
 
 To export a module, right-click a module in the **App Explorer**, and select **Export module package**.
 
+If your module contains files with paths that are not allowed in module packages, Studio Pro shows a warning listing the affected paths before you choose where to save the package. Studio Pro cannot import such a package. Review and correct the file paths before distributing the module. Contact Mendix Support if you need assistance.
+
+Disallowed paths are the same as those listed above for importing, as well as path-traversal patterns (for example, `../../`):
+
+* directories starting with '.'
+* releases/
+* packages/
+* deployment/
+* nativemobile/builds/
+* vendorlib/temp/
+* mprcontents/
+
+{{% alert color="warning" %}}
+In an upcoming version of Studio Pro, exporting a module that contains files with disallowed paths will also not be possible. Make sure all file paths in your module package are valid to avoid issues later.
+{{% /alert %}}
+
 If your module refers to other modules in the app (that is, it is not self-contained), you will see a warning pop-up window.
 
 Select **Find usages of other user modules** to view the references, or click **Continue exporting** and you will see the **Select Dependencies** dialog box: