Cross-link Workers docs and clarify per-Worker vs account-level

Author: RebeccaTamachiro

src/content/docs/workers/configuration/environment-variables.mdx

@@ -90,9 +90,7 @@ To add environment variables via the dashboard:
 8. Select **Deploy** to implement your changes.
 
 :::caution[Plaintext strings and secrets]
-
-Select the **Secret** type if your environment variable is a [secret](/workers/configuration/secrets/).
-
+Select the **Secret** type if your environment variable is a [secret](/workers/configuration/secrets/). Alternatively, consider [Cloudflare Secrets Store](/secrets-store/), for account-level secrets.
 :::
 
 <Render file="env_and_secrets" />

src/content/docs/workers/configuration/secrets.mdx

@@ -11,6 +11,10 @@ import { Render } from "~/components";
 
 Secrets are a type of binding that allow you to attach encrypted text values to your Worker. You cannot see secrets after you set them and can only access secrets via [Wrangler](/workers/wrangler/commands/#secret) or programmatically via the [`env` parameter](/workers/runtime-apis/handlers/fetch/#parameters). Secrets are used for storing sensitive information like API keys and auth tokens. Secrets are available on the [`env` parameter](/workers/runtime-apis/handlers/fetch/#parameters) passed to your Worker's [`fetch` event handler](/workers/runtime-apis/handlers/fetch/).
 
+:::note[Secrets Store (beta)]
+Secrets described on this page are defined and managed on a per-Worker level. If you want to use account-level secrets, refer to [Secrets Store](/secrets-store/). Account-level secrets are configured on your Worker as a [Secrets Store binding](/secrets-store/integrations/workers/).
+:::
+
 ## Local Development with Secrets
 
 <Render file="secrets-in-dev" />
@@ -86,3 +90,4 @@ To delete a secret from your Worker project via the dashboard:
 ## Related resources
 
 - [Wrangler secret commands](/workers/wrangler/commands/#secret) - Review the Wrangler commands to create, delete and list secrets.
+- [Cloudflare Secrets Store](/secrets-store/) - Encrypt and store sensitive information as secrets that are securely reusable across your account.

src/content/docs/workers/runtime-apis/bindings/secrets-store.mdx

@@ -0,0 +1,8 @@
+---
+pcx_content_type: navigation
+title: Secrets Store (Beta)
+external_link: /secrets-store/integrations/workers/
+head: []
+description: Account-level secrets that can be added to Workers applications as a binding.
+
+---

src/content/partials/workers/env_and_secrets.mdx

@@ -6,11 +6,7 @@
 ## Compare secrets and environment variables
 
 :::caution[Use secrets for sensitive information]
-
-
-Do not use plaintext environment variables to store sensitive information. Use [secrets](/workers/configuration/secrets/) instead.
-
-
+Do not use plaintext environment variables to store sensitive information. Use [secrets](/workers/configuration/secrets/) or [Secrets Store bindings](/secrets-store/integrations/workers/) instead.
 :::
 
 [Secrets](/workers/configuration/secrets/) are [environment variables](/workers/configuration/environment-variables/). The difference is secret values are not visible within Wrangler or Cloudflare dashboard after you define them. This means that sensitive data, including passwords or API tokens, should always be encrypted to prevent data leaks. To your Worker, there is no difference between an environment variable and a secret. The secret's value is passed through as defined.