diff --git a/docs/documentation/platform/folder.mdx b/docs/documentation/platform/folder.mdx
index 716cb4e46..e285967cd 100644
--- a/docs/documentation/platform/folder.mdx
+++ b/docs/documentation/platform/folder.mdx
@@ -37,6 +37,8 @@ For more information on integrations, [refer infisical integration](/integration
 
 You can scope the secrets that can be read and written using an Infisical token by providing the secret path option when creating the token.
 
+You can provide the folder path as glob if you want to have access to multiple folders and the tokens do support multi-environment.
+
 ![folder scoped service token](../../images/project-folder-token.png)
 
 For more information, [refer infisical token section.](./token)
diff --git a/docs/documentation/platform/secret-reference.mdx b/docs/documentation/platform/secret-reference.mdx
new file mode 100644
index 000000000..663f4ca78
--- /dev/null
+++ b/docs/documentation/platform/secret-reference.mdx
@@ -0,0 +1,26 @@
+---
+title: "Reference Secrets"
+description: "How to use reference secrets in Infisical"
+---
+
+You can use the interpolation syntax to reference a secret in the same environment, another folder, or another environment
+The interpolation syntax is a way of referencing a secret by using a special placeholder. The placeholder is the name of the secret, followed by the environment or folder name, separated by a colon. 
+
+For example, to reference a secret named mysecret in the same environment, you would use the placeholder ${mysecret}.
+
+While for another environment like `test` would be ${test.mysecret}
+
+Some more examples of referencing  are 
+
+| Syntax                | Environment | Folder       | Secret Key |
+| --------------------- | ----------- | ------------ | ---------- |
+| ${KEY1}               | same env    | ssame folder | KEY1       |
+| ${dev.KEY2}           | dev         | /            | KEY2       |
+| ${test.frontend.KEY2} | test        | /frontend    | KEY2       |
+
+# Permission system for reference
+
+When you use the infisical CLI to log in, the permission system will work the same way as your user permissions. 
+This means that if you have permission to access other environments, your references to those environments will be resolved.
+
+When using the Infisical CLI with a service token, the service token must have permissions to the referenced environment and folder path.
diff --git a/docs/images/project-folder-token.png b/docs/images/project-folder-token.png
index 4fda56d27..2402acdf2 100644
Binary files a/docs/images/project-folder-token.png and b/docs/images/project-folder-token.png differ
diff --git a/docs/mint.json b/docs/mint.json
index ba66b271f..25db15c63 100644
--- a/docs/mint.json
+++ b/docs/mint.json
@@ -110,6 +110,7 @@
         "documentation/platform/organization",
         "documentation/platform/project",
         "documentation/platform/folder",
+        "documentation/platform/secret-reference",
         "documentation/platform/pit-recovery",
         "documentation/platform/secret-versioning",
         "documentation/platform/audit-logs",