Skip to content

docs: team name lives under Zero Trust Settings - #33076

Open
AiAlchemist0 wants to merge 1 commit into
cloudflare:productionfrom
AiAlchemist0:docs/zero-trust-team-name
Open

docs: team name lives under Zero Trust Settings#33076
AiAlchemist0 wants to merge 1 commit into
cloudflare:productionfrom
AiAlchemist0:docs/zero-trust-team-name

Conversation

@AiAlchemist0

Copy link
Copy Markdown
Contributor

Fixes #32894

The shared team-name snippet said Settings under the Cloudflare dashboard. Team name is under Zero Trust, same path as the onboarding page. One partial, so every identity-provider page that uses it picks this up.

@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Review

✅ No issues found in commit ac1ef70.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

No code review issues found.

Conventions

No convention issues found.

Style Guide Review

No style-guide issues found.

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Team Name Route Incorrect in Documentation

1 participant