[Flagship] Document app-scoped API tokens - #32851
Open
roerohan wants to merge 8 commits into
Open
Conversation
roerohan
requested review from
a team,
akshitsinha and
palashgo
as code owners
August 19, 2026 09:15
Contributor
Review
👉 Fix in your agent 👈Fix the following review findings in PR #32851 (https://github.com/cloudflare/cloudflare-docs/pull/32851).
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
### Warnings (1)
#### SG-7b8b3abd8e29 · MDX docs should use <TypeScriptExample> for TypeScript/JS code blocks
- **File:** `src/content/docs/flagship/api-tokens.mdx` line 92
- **Issue:** Line 92 starts a raw ` ```ts ` fenced block in a docs MDX file.
- **Fix:** Replace the raw TypeScript fence with the `<TypeScriptExample>` component.
### Suggestions (1)
#### SG-a76481c4e0b6 · Bullet lists should have at least three items or be written as prose
- **File:** `src/content/docs/flagship/api-tokens.mdx` line 111
- **Issue:** The Next steps section contains a two-item bullet list (lines 111–112).
- **Fix:** Consider rewriting the two Next steps as prose sentences instead of a bullet list.
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 ReviewWarnings (1)
Suggestions (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:
|
roerohan
force-pushed
the
flagship/app-scoped-tokens
branch
from
August 19, 2026 09:30
a86f8df to
6af60ac
Compare
akshitsinha
approved these changes
Aug 19, 2026
Contributor
MohamedH1998
approved these changes
Aug 19, 2026
irvinebroque
approved these changes
Aug 19, 2026
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://flagship-app-scoped-tokens-cloudflare-docs.cloudflare-docs.workers.dev (commit 08f0c0e)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Add a changelog for 2026-08-19, a how-to for creating tokens scoped to a single Flagship app, and update the client SDK warning so browsers can use Flagship App Evaluate instead of an account-wide token.
Rewrite the token page around the dashboard flow: Entire Account vs Specified Flagship apps, then pick the app and a Flagship App permission.
Add the dashboard deeplink that opens Specified Flagship apps with Flagship App Evaluate selected.
Mirror the app-scoped deeplink with a plain Account API tokens link for the account-wide flow.
Keep app-scoped tokens documented for server-side least privilege. Restore the client SDK warning and drop any guidance that puts tokens in the browser.
roerohan
force-pushed
the
flagship/app-scoped-tokens
branch
from
August 21, 2026 10:49
d8bb18d to
67cb27b
Compare
This release is app-scoped tokens only. Client-side evaluation is follow-up work.
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
6 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
Document Flagship app-scoped API tokens. Customers can now create a token that only evaluates or manages the Flagship apps they select, instead of every app in the account.
/flagship/api-tokens/for account-wide and app-scoped tokens.This PR does not change client-side evaluation guidance. A dedicated client key is follow-up work.
Documentation checklist