Skip to content

Mleslie cf/casb zoom support#32120

Open
mleslie-cf wants to merge 2 commits into
cloudflare:productionfrom
mleslie-cf:mleslie-cf/casb-zoom-support
Open

Mleslie cf/casb zoom support#32120
mleslie-cf wants to merge 2 commits into
cloudflare:productionfrom
mleslie-cf:mleslie-cf/casb-zoom-support

Conversation

@mleslie-cf

Copy link
Copy Markdown
Contributor

Summary

  • Adding standard Cloudflare One vendor documentation for Zoom

Documentation checklist

  • [ x] Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • [x ] The change adheres to the documentation style guide.
  • [x ] If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • [n/a ] Files which have changed name or location have been allocated redirects.

@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Review

⚠️ 4 warnings, 💡 2 suggestions found in commit c72ad57.

Fix in your agent
Fix the following review findings in PR #32120 (https://github.com/cloudflare/cloudflare-docs/pull/32120).

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, fix all legitimate findings. For any you decide to skip,
post a comment on this PR with the finding ID and your reasoning.

---

## Conventions

### Warnings (1)

#### CV-e15c7ce86642 · PR title format
- **File:** PR-level finding
- **Issue:** Title 'Mleslie cf/casb zoom support' does not clearly identify the product or content area; 'Mleslie' and 'cf/casb' read as a username/branch prefix and ambiguous shorthand rather than naming the docs area.
- **Fix:** Name the affected product/feature in the title, e.g. 'Cloudflare One CASB: Add Zoom integration docs'.

---

## Style Guide Review

### Warnings (3)

#### SG-f717d6e51a43 · Heading begins with -ing verb
- **File:** `src/content/docs/cloudflare-one/integrations/cloud-and-saas/zoom.mdx` line 34
- **Issue:** ## Adding the app
- **Fix:** Change to `## Add the app`

#### SG-bd483157af48 · Heading begins with -ing verb
- **File:** `src/content/docs/cloudflare-one/integrations/cloud-and-saas/zoom.mdx` line 110
- **Issue:** ### Content scanning
- **Fix:** Change to `### Content scan`

#### SG-dd4542bc9ac1 · Heading begins with -ing verb
- **File:** `src/content/docs/cloudflare-one/integrations/cloud-and-saas/zoom.mdx` line 244
- **Issue:** ## Removing the app
- **Fix:** Change to `## Remove the app`

### Suggestions (2)

#### SG-065f4732870a · Spell out single-digit numerals
- **File:** `src/content/docs/cloudflare-one/integrations/cloud-and-saas/zoom.mdx` line 32
- **Issue:** free plan supports up to `2` integrations
- **Fix:** Change to `two integrations`

#### SG-3dc671e859a9 · Use direct 'refer to' phrasing for links
- **File:** `src/content/docs/cloudflare-one/integrations/cloud-and-saas/zoom.mdx` line 100
- **Issue:** To learn more about each scope, refer to the [Zoom API scopes reference]
- **Fix:** Use `For more information, refer to [Zoom API scopes reference](https://developers.zoom.us/docs/api/)`

Code Review

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

No code review issues found.

Conventions

Warnings (1)
File Issue
PR PR title format — Title 'Mleslie cf/casb zoom support' does not clearly identify the product or content area; 'Mleslie' and 'cf/casb' read as a username/branch prefix and ambiguous shorthand rather than naming the docs area. Fix: Name the affected product/feature in the title, e.g. 'Cloudflare One CASB: Add Zoom integration docs'.

Style Guide Review

Warnings (3)
File Issue
cloudflare-one/integrations/cloud-and-saas/zoom.mdx line 34 Heading begins with -ing verb — ## Adding the app Fix: Change to ## Add the app
cloudflare-one/integrations/cloud-and-saas/zoom.mdx line 110 Heading begins with -ing verb — ### Content scanning Fix: Change to ### Content scan
cloudflare-one/integrations/cloud-and-saas/zoom.mdx line 244 Heading begins with -ing verb — ## Removing the app Fix: Change to ## Remove the app
Suggestions (2)
File Issue
cloudflare-one/integrations/cloud-and-saas/zoom.mdx line 32 Spell out single-digit numerals — free plan supports up to 2 integrations Fix: Change to two integrations
cloudflare-one/integrations/cloud-and-saas/zoom.mdx line 100 Use direct 'refer to' phrasing for links — To learn more about each scope, refer to the [Zoom API scopes reference] Fix: Use For more information, refer to [Zoom API scopes reference](https://developers.zoom.us/docs/api/)
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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants