Skip to content

Commit e3576a2

Browse files
authored
Changelog for reusable Access policies for Workers (#26911)
1 parent 1258630 commit e3576a2

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: One-click Access protection for Workers now creates reusable Cloudflare Access policies
3+
description: Workers now use reusable Access policies to reduce duplication and make it easier to manage access across multiple Workers.
4+
products:
5+
- workers
6+
date: 2025-12-04
7+
---
8+
9+
Workers applications now use reusable [Cloudflare Access policies](/cloudflare-one/access-controls/policies/) to reduce duplication and simplify access management across multiple Workers.
10+
11+
Previously, enabling Cloudflare Access on a Worker created per-application policies, unique to each application. Now, we create reusable policies that can be shared across applications:
12+
13+
- **Preview URLs**: All Workers preview URLs share a single "Cloudflare Workers Preview URLs" policy across your account. This policy is automatically created the first time you enable Access on any preview URL. By sharing a single policy across all preview URLs, you can configure access rules once and have them apply company-wide to all Workers which protect preview URLs. This makes it much easier to manage who can access preview environments without having to update individual policies for each Worker.
14+
15+
- **Production workers.dev URLs**: When enabled, each Worker gets its own reusable policy (named `<worker-name> - Production`) by default. We recognize production services often have different access requirements and having individual policies here makes it easier to configure service-to-service authentication or protect internal dashboards or applications with specific user groups. Keeping these policies separate gives you the flexibility to configure exactly the right access rules for each production service. When you disable Access on a production Worker, the associated policy is automatically cleaned up if it's not being used by other applications.
16+
17+
This change reduces policy duplication, simplifies cross-company access management for preview environments, and provides the flexibility needed for production services. You can still customize access rules by editing the reusable policies in the Zero Trust dashboard.
18+
19+
To enable Cloudflare Access on your Worker:
20+
21+
1. In the Cloudflare dashboard, go to **Workers & Pages**.
22+
2. Select your Worker.
23+
3. Go to **Settings** > **Domains & Routes**.
24+
4. For `workers.dev` or Preview URLs, click **Enable Cloudflare Access**.
25+
5. Optionally, click **Manage Cloudflare Access** to customize the policy.
26+
27+
For more information on configuring Cloudflare Access for Workers, refer to the [Workers Access documentation](/workers/configuration/routing/workers-dev/#cloudflare-access).

0 commit comments

Comments
 (0)