Add Workers KV jurisdictions documentation - #32357
Open
rts-rob wants to merge 1 commit into
Open
Conversation
rts-rob
requested review from
a team,
Oxyjun,
elithrar and
thomasgauvin
as code owners
July 28, 2026 14:00
Contributor
Review💡 1 suggestion found in commit 👉 Fix in your agent 👈Fix the following review findings in PR #32357 (https://github.com/cloudflare/cloudflare-docs/pull/32357).
Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order
After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.
The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.
---
## Style Guide Review
### Suggestions (1)
#### SG-6cf46cc6abed · Passive voice
- **File:** `src/content/docs/kv/concepts/kv-namespaces.mdx` line 24
- **Issue:** Line uses "Namespaces can optionally be restricted", which is passive.
- **Fix:** Rewrite in active voice, e.g. "You can optionally restrict namespaces to a jurisdiction..."
Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewSuggestions (1)
CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
/rebase |
Add a new data location reference page documenting how to restrict a KV namespace to a jurisdiction (EU, FedRAMP, US) for compliance purposes, currently in private beta. Link to it from the KV namespaces concept page and the KV product index.
cloudflare-docs-bot
Bot
force-pushed
the
rsutter/kv-jurisdictions
branch
from
July 28, 2026 14:14
d8cc4eb to
89ccdb0
Compare
Contributor
vy-ton
reviewed
Jul 28, 2026
rts-rob
enabled auto-merge (squash)
July 29, 2026 09:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new reference page documenting Workers KV jurisdictions, which allow a KV namespace to be restricted to store and process data only within a specific region (EU, FedRAMP, US) to help meet compliance requirements. This feature is currently in private beta.
/kv/reference/data-location/covering automatic (default) data location, how to restrict a namespace to a jurisdiction, supported jurisdictions, and how to request access.Screenshots (optional)
N/A
Documentation checklist