docs: public beta, all plans, remove internal references

Author: wevans997-dev

src/content/changelog/resource-tagging/2026-01-28-resource-tagging-private-beta.mdx

@@ -1,10 +1,10 @@
 ---
-title: Resource Tagging enters private beta
-description: Enterprise customers can now attach key-value metadata to Cloudflare resources via API.
+title: Resource Tagging enters public beta
+description: Cloudflare customers can now attach key-value metadata to resources via API.
 date: 2026-01-28
 ---
 
-Resource Tagging is now available in private beta for Enterprise customers. The feature enables attaching custom key-value metadata to Cloudflare resources for organization, access control, and billing attribution.
+Resource Tagging is now available in public beta. The feature enables attaching custom key-value metadata to Cloudflare resources for organization, access control, and billing attribution.
 
 ### What's included
 

src/content/changelog/resource-tagging/2026-03-25-expanded-roles-and-aot-updates.mdx

@@ -14,8 +14,8 @@ Tag management is no longer limited to Super Administrators. The following roles
 
 ### AOT provisioning change
 
-Account Owned Tokens for tagging are now **created on behalf of customers** by the GRM team. Customers can view their tokens but cannot modify them directly. This simplifies onboarding and ensures tokens have the correct permissions from the start.
+Account Owned Tokens for tagging are now **provisioned on behalf of customers**. Customers can view their tokens but cannot modify them directly. This simplifies onboarding and ensures tokens have the correct permissions from the start.
 
 ### Dashboard UI in development
 
-The Stratus-based Dashboard UI for resource tagging is in active development. A staging preview is available behind the `resource-tagging-ui-experiments` gate. The Dashboard experience will complement (not replace) the existing API.
+The Dashboard UI for resource tagging is in active development. The Dashboard experience will complement (not replace) the existing API.

src/content/docs/resource-tagging/get-started.mdx

@@ -3,37 +3,20 @@ title: Get started
 pcx_content_type: get-started
 sidebar:
   order: 2
-description: Enable Resource Tagging for a customer account and make your first API calls.
+description: Set up authentication for Resource Tagging and make your first API calls.
 ---
 
-This guide walks you through enabling tagging for an Enterprise account and verifying it works.
+This guide walks you through verifying that tagging works on your account and making your first API calls.
 
 ## Prerequisites
 
-Before enabling Resource Tagging, ensure the account meets these requirements:
-
-- **Enterprise plan** -- Resource Tagging is only available to Enterprise customers.
 - **Super Admin access** -- At least one user with the Super Administrator, Workers Admin, or Tag Admin role. These roles can create, update, and delete tags.
-- **API familiarity** -- The feature is API-only during the private beta. Customers must be comfortable making authenticated HTTP requests.
-
-## 1. Request enablement
-
-Contact PM Wesley Evans to request tagging enablement for a customer account:
-
-- **G-Chat**: Join the "Tags for Cloudflare" space for real-time support
-- **Email**: wesley.evans@cloudflare.com
+- **API familiarity** -- The feature is API-only during the beta. You should be comfortable making authenticated HTTP requests.
+- **API token** -- An API token with the required [permissions](/resource-tagging/reference/api/#required-permissions). [Account Owned Tokens (AOTs)](/fundamentals/api/get-started/account-owned-tokens/) are recommended for automation.
 
-Provide the following:
+## 1. Verify tagging is enabled
 
-- **Account ID** -- The customer's Cloudflare account ID, found in the Dashboard URL or via `GET /accounts`.
-- **Use case** -- A brief description of how the customer plans to use tagging (1-2 sentences).
-- **Products to be tagged** -- Which resource types the customer plans to tag initially (for example, `workers_script`, `zone`, `custom_hostnames`).
-
-Wesley will enable the feature via [gates.cloudflare.com](https://gates.cloudflare.com). Typical turnaround is 1-2 business days.
-
-## 2. Verify tagging is enabled
-
-After receiving enablement confirmation, test the API:
+Test the API to confirm tagging is active on your account:
 
 ```bash
 curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags/keys" \
@@ -45,17 +28,13 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags/keys
 
 | Response | Meaning | Action |
 | --- | --- | --- |
-| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed with onboarding. |
-| **403** mentioning "permission" or "role" | The caller lacks required permissions. This is not a gating issue. | Verify the caller has Super Admin role or the token has `#com.cloudflare.api.account.tag.list` scope. |
-| **403** mentioning "feature" or "gate" | Tagging is not enabled for this account. | Confirm the Account ID matches what was provided to Wesley. Contact the Tags for Cloudflare G-Chat space. |
+| **200 OK** with `{"success": true, "result": [...]}` | Tagging is enabled. An empty array is normal if no tags exist yet. | Proceed to the next step. |
+| **403** mentioning "permission" or "role" | The caller lacks required permissions. | Verify the caller has a Super Admin, Workers Admin, or Tag Admin role, or that the token has `#com.cloudflare.api.account.tag.list` scope. |
+| **403** mentioning "feature" or "gate" | Tagging is not enabled for this account. | Contact [Cloudflare support](/support/contacting-cloudflare-support/) for assistance. |
 | **401 Unauthorized** | Authentication failed. | Verify the token is valid, not expired, and formatted correctly in the `Authorization: Bearer` header. |
-| Any other response | Unexpected error. | Capture the full response body and escalate to the Tags for Cloudflare G-Chat space with the Account ID, request details, and timestamp. |
-
-:::note
-Gate changes typically propagate within seconds, but may take up to 15 minutes in rare cases. If you receive a gating error immediately after enablement, wait briefly and retry.
-:::
+| Any other response | Unexpected error. | Capture the full response body and contact [Cloudflare support](/support/contacting-cloudflare-support/) with the Account ID, request details, and timestamp. |
 
-## 3. Create your first tags
+## 2. Create your first tags
 
 Set tags on a resource using `PUT`:
 
@@ -81,7 +60,7 @@ curl -X GET "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tags?reso
   -H "Content-Type: application/json"
 ```
 
-## 4. List tagged resources
+## 3. List tagged resources
 
 Query all tagged resources in the account, optionally filtering by tag:
 

src/content/docs/resource-tagging/index.mdx

@@ -16,22 +16,14 @@ Attach custom key-value metadata to Cloudflare resources for organization, acces
 
 </Description>
 
-<Plan type="enterprise" />
+<Plan type="all" />
 
 Resource Tagging lets you attach key-value pairs to Cloudflare resources like Workers scripts, zones, custom hostnames, and Access application policies. Tags are stored separately from the resources themselves, enabling cross-resource queries and policy enforcement without modifying underlying resource configurations.
 
-:::note[Private beta]
-Resource Tagging is currently in private beta and available exclusively to Enterprise customers. The API is stable, but behavior may change as we iterate based on feedback.
+:::note[Public beta]
+Resource Tagging is in public beta. The API is stable, but behavior may change as we iterate based on feedback.
 :::
 
-## Key use cases
-
-- **Resource grouping** -- Track and manage resources across teams, products, or projects. Tag all resources belonging to a team or product line for bulk operations and inventory management.
-- **Access control** -- Implement fine-grained permission policies based on tags. Restrict user access to resources tagged with specific values like `environment=production` or `team=platform-engineering`.
-- **Billing attribution** -- Allocate costs by business context. Tag resources with cost centers, departments, or projects for chargeback reports.
-- **Environment management** -- Distinguish production from non-production resources. Apply tags like `environment=staging` to enforce different policies or deployment workflows.
-- **Ownership tracking** -- Identify resource owners and responsible teams for incident response and maintenance scheduling.
-
 ## How it works
 
 Tags are simple key-value string pairs stored as a JSON object:
@@ -50,11 +42,11 @@ Authentication uses [Account Owned Tokens (AOTs)](/fundamentals/api/get-started/
 
 ## Limitations
 
-- **API-only** -- There is no Dashboard UI during the private beta. A Dashboard experience is in active development.
+- **API-only** -- There is no Dashboard UI during the beta. A Dashboard experience is in active development.
 - **PUT replaces all tags** -- There is no PATCH endpoint. The `PUT` operation replaces all tags on a resource. Use the [GET, merge, PUT workflow](/resource-tagging/how-to/manage-tags/#add-a-single-tag) to modify individual tags.
 - **DELETE removes all tags** -- There is no way to delete a single tag. Use `PUT` with the remaining tags instead.
 - **500 on untagged resources** -- Querying tags for a resource that has never been tagged returns a `500` error instead of `404`. This is a known beta limitation.
 
 ## Get started
 
-Follow the [Get started guide](/resource-tagging/get-started/) to enable tagging for a customer account and make your first API calls.
+Follow the [Get started guide](/resource-tagging/get-started/) to set up authentication and make your first API calls.

src/content/docs/resource-tagging/reference/api.mdx

@@ -6,11 +6,6 @@ sidebar:
 description: Tagging API endpoints, authentication, and common response patterns.
 ---
 
-The Tagging API is verified against OpenAPI spec v4.0.1. Full machine-readable specs are available on Backstage:
-
-- [Public API spec](https://backstage.cfdata.org/catalog/default/api/resource-tagging-v4-api/definition)
-- [Internal admin API spec](https://backstage.cfdata.org/catalog/default/api/resource-tagging-admin-api/definition)
-
 ## Base URL
 
 ```