From abbf3e80f9f68021f60ff9a9e2308ca1f12f5cdc Mon Sep 17 00:00:00 2001 From: Maidul Islam Date: Wed, 19 Jul 2023 00:31:45 -0400 Subject: [PATCH] Update secret-reference.mdx --- docs/documentation/platform/secret-reference.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/platform/secret-reference.mdx b/docs/documentation/platform/secret-reference.mdx index 8df6fce72..ffae77e2b 100644 --- a/docs/documentation/platform/secret-reference.mdx +++ b/docs/documentation/platform/secret-reference.mdx @@ -29,7 +29,7 @@ Here are a few more examples to help you understand how to reference secrets in ## Fetching fully constructed values Secret referencing combines multiple secrets into one unified value, reconstructed only on the client side. To retrieve this value, you need access to read the environment and [folder](./folder) from where the secrets originate. -For instance, to access a secret 'A' composed of secrets 'B' and 'C' from different environments, you must have read access to both. +For instance, to access a secret 'A' composed of secrets 'B' and 'C' from different environments, you must have read access to both 'A' and 'B' When using [service tokens](./token) to fetch referenced secrets, ensure the service token has read access to all referenced environments and folders. Without proper permissions, the final secret value may be incomplete.