Automation hub, team and org scoped automations - #2959
Conversation
HiveMind Sessions1 session · 31m · $5.27
View all sessions in HiveMind → Run |
There was a problem hiding this comment.
Pull request overview
Adds documentation for the global Automations hub and expands Automations docs to cover Organization- and Team-scoped automations, including where to create them, what events are available at broader scopes, and how to view execution history.
Changes:
- Introduces the Automations hub concept and updates “where to find/create” guidance to include hub-based workflows.
- Adds Organization/Team scope definitions and event availability details (including rate limiting/cooldown note).
- Updates Slack/Webhook automation creation docs and automation history docs to reflect hub + broader scopes.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| snippets/_includes/automations/where-to-find-automations.mdx | Adds the Automations hub as a primary discovery/entry point across scopes. |
| models/automations.mdx | Expands scope model, adds an Automations hub section, and updates limitations text. |
| models/automations/automation-events.mdx | Adds Organization and Team scope sections and contextual notes about triggering behavior. |
| models/automations/create-automations.mdx | Updates creation entry points to include the global Automations hub + scope selection. |
| models/automations/create-automations/webhook.mdx | Adds a note directing readers to hub-based Team/Org scope creation and scope limitations. |
| models/automations/create-automations/slack.mdx | Adds a note directing readers to hub-based Team/Org scope creation and scope limitations. |
| models/automations/view-automation-history.mdx | Adds hub-based guidance for viewing history across scopes, plus registry/project alternatives. |
Comments suppressed due to low confidence (1)
models/automations.mdx:81
- Typo: "webhoook" should be "webhook".
- At the **Team** and **Organization** scopes, the W&B App supports only artifact and collection events. Run-based events aren't available in the App at these scopes. See [Automation events and scopes](/models/automations/automation-events).
## Next steps
- [Automations tutorial](/models/automations/tutorial): Guides you to create a project automation to alert on run failures and a Registry automation to run a webhoook when an alias is added. The tutorial uses the W&B App.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
📚 Mintlify Preview Links📝 Changed (7 total)📄 Pages (7)
🤖 Generated automatically when Mintlify deployment succeeds |
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Preview: https://wb-21fd5541-automation-updates-docs-2928-docs-2829.mintlify.site |
- Fix broken anchors in automations.mdx Limitations (run-metrics-change, run-metrics-z-score-change) and fix "webhoook" typo in Next steps. - Add a Team/Org scope availability note to automation-events.mdx. - Qualify hub-based history guidance in view-automation-history.mdx: lead with the always-available registry/project tabs and gate the Automations hub to Multi-tenant/Dedicated (Server v0.83.0+). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Readability impactWord-weighted Flesch-Kincaid grade change across 6 changed pages: +0.1 (harder). Lower Flesch-Kincaid grade and higher reading ease both mean easier to read. This check is informational and never blocks a PR. Human readability
AI agent comprehensionRated 0-3 (higher is easier for an agent to parse and act on).
Curated-docs baseline median FK grade by type: conceptual 10.5, procedural 8.8, reference 9.4. |
Co-authored-by: Matt Linville <matt@linville.me>
| ## Limitations | ||
| [Run metric automations](/models/automations/automation-events/#run-metrics-events) and [run metrics z-score change automations](/models/automations/automation-events/#run-metrics-z-score-change-automations) are currently supported only in [W&B Multi-tenant Cloud](/platform/hosting/#wb-multi-tenant-cloud). | ||
| - [Run metric automations](/models/automations/automation-events/#run-metrics-change) and [run metrics z-score change automations](/models/automations/automation-events/#run-metrics-z-score-change) are supported only in [W&B Multi-tenant Cloud](/platform/hosting/#wb-multi-tenant-cloud) and [Dedicated Cloud](/platform/hosting/hosting-options/dedicated-cloud). | ||
| - At the **Team** and **Organization** scopes, the W&B App supports only artifact and collection events. Run-based events aren't available in the App at these scopes. See [Automation events and scopes](/models/automations/automation-events). |
There was a problem hiding this comment.
Not sure if you mention this elsewhere, but it is possible to create team-/org-scoped run automations programmatically (via the Automations API in the SDK). At least it will be -- pending the following PR (still in review): wandb/wandb#12194
suggestion: May be worth mentioning the programmatic (SDK) API does allow these, to avoid undue confusion
Extra context:
- Run automations aren't outright disabled for team/org scopes, they're just hidden in the (more curated) UI
- The fact that we hid them in the UI was a late-game decision. Not essential for this PR, but for reference, some context for the decision: thread
Description
Docs for Automations Hub, team-scoped automations, and org-scoped automations. These features shipped with 0.83.0.
Available for technical review
Fixes DOCS-2928
Fixes DOCS-2929
Testing
mint dev)mint broken-links)