Skip to content

Commit 6b91071

Browse files
Further dash options and align with other binding docs
1 parent 4053e7a commit 6b91071

File tree

1 file changed

+17
-11
lines changed

1 file changed

+17
-11
lines changed

src/content/docs/secrets-store/integrations/workers.mdx

Lines changed: 17 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -14,18 +14,19 @@ This is different from Workers [Variables and Secrets](/workers/configuration/se
1414

1515
## Before you begin
1616

17-
If [using the Dashboard](#option-b-use-the-dashboard), make sure you already have a Workers application. Refer to [Get started](/workers/get-started/dashboard/) for guidance.
17+
If [using the Dashboard](#option-b-via-dashboard), make sure you already have a Workers application. Refer to [Get started](/workers/get-started/dashboard/) for guidance.
1818

1919
## 1. Set up account secrets in Secrets Store
2020

2121
If there are no account secrets yet, follow the steps below. You must have a (TBC) [Super Administrator or a Secrets Store Admin role](/secrets-store/access-control/) within your Cloudflare account.
2222

23-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
24-
2. Go to **Secrets Store** and select **Create secret**.
25-
3. Fill in the required fields, choosing _Workers_ as the **Permission scope**.
2623
:::note
27-
Once the secret is saved, the secret value will no longer be available for viewing.
24+
You may also add account secrets directly from the Workers settings on the dashboard. You can skip to [step 2](#option-b-via-dashboard) to do that.
2825
:::
26+
27+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
28+
2. Go to **Secrets Store** and select **Create secret**.
29+
3. Fill in the required fields, choosing _Workers_ as the **Permission scope**. Once the secret is saved, the secret value will no longer be available for viewing.
2930
4. (Optional) Select **Add additional secret** to create more than one secret at a time.
3031
5. Select **Save** to confirm
3132

@@ -38,15 +39,20 @@ Refer to [manage account secrets](/secrets-store/manage-secrets/) for further op
3839
- Secrets Store Admin
3940
- Secrets Store Deploy
4041

41-
### Option A: use the CLI
42+
### Option A: via Wrangler
4243

43-
### Option B: use the Dashboard
44+
### Option B: via Dashboard
4445

4546
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
46-
2. Go to **Workers & Pages** and select the Workers application where you want ro use account secrets.
47-
3. Got to **Settings** > **Bindings** and select **Add**.
47+
2. Go to **Workers & Pages** and select a Workers application.
48+
3. Go to **Settings** > **Bindings** and select **Add**.
4849
4. On the **Add a resource binding** side panel, choose **Secrets Store**.
49-
5. Select the **Secret name** from the list of available account secrets (created in [step 1](#1-set-up-account-secrets-in-secrets-store)).
50-
6. Select **Deploy** to confirm.
50+
5. Fill in the required fields:
51+
- **Variable name**: a name for the binding. This will be used for your worker to access the secret ([step 3](#3-access-the-secret-on-the-env-object) below).
52+
- **Secret name**: select from the list of available account secrets created in [step 1](#1-set-up-account-secrets-in-secrets-store).
53+
- (Optional - Admins only) If the secret you need does not exist yet, select **Create secret**. This will add an account level secret in the same way as if you had [created it on the Secrets Store](/secrets-store/manage-secrets/).
54+
6. Select **Deploy** to deploy your binding. When deploying, there are two options:
55+
- **Deploy:** Immediately deploy the binding to 100% of your audience.
56+
- **Save version:** Save a version of the binding which you can deploy in the future.
5157

5258
## 3. Access the secret on the `env` object

0 commit comments

Comments
 (0)