diff --git a/CHANGELOG.md b/CHANGELOG.md
index 314572b88..8a98a918e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,6 +13,7 @@
         - Modified composer scripts to handle missing PHP extensions
         - Removed abandoned leafo/scssphp package in favor of scssphp/scssphp
         - Removed support for PHP versions below 8.1
+        - Added documentation about CSP requirements - 'unsafe-eval' is needed for admin functionality (#3255)
     3. [](#bugfix)
         - Fixed incorrect formatting in changelog file (#3305)
         - Fixed missing translation on WordPress for "Content" tab (#3302)
diff --git a/CSP-REQUIREMENTS.md b/CSP-REQUIREMENTS.md
new file mode 100644
index 000000000..32389cbe9
--- /dev/null
+++ b/CSP-REQUIREMENTS.md
@@ -0,0 +1,41 @@
+# Gantry 5 Content Security Policy (CSP) Requirements
+
+## Overview
+
+[Content Security Policy (CSP)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) is a security mechanism that helps prevent Cross-Site Scripting (XSS) and data injection attacks. While using strict CSP settings is generally recommended for websites, Gantry 5 requires certain CSP directives to function properly in the administrator area.
+
+## Required CSP Directives
+
+Gantry 5 administration requires the following CSP directives:
+
+```
+script-src 'self' 'unsafe-eval';
+```
+
+The `unsafe-eval` directive is specifically needed for:
+- Cache clearing operations
+- Editing functionality
+- JSON parsing and handling
+- Various admin UI interactions
+
+## Example CSP Header for Admin Area
+
+```
+Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;
+```
+
+## Recommendations
+
+1. **Split CSP Policies**:
+   - Use a stricter policy for your frontend website
+   - Use a more permissive policy with `unsafe-eval` for the admin area only
+
+2. **Security Balance**:
+   - Consider keeping `unsafe-eval` only in the administrator sections of your site
+   - Use stricter CSP settings for all public-facing pages
+
+## Technical Explanation
+
+Gantry 5 uses JavaScript bundling tools like Browserify which rely on `eval()` or `new Function()` constructs for certain operations. Additionally, the dynamic nature of the admin interface requires runtime code evaluation in some cases.
+
+These requirements may change in future versions as we continue to improve Gantry's CSP compatibility.
\ No newline at end of file