Team wide workflows (beta)
Standardize repeatable agent work across a team.
A team workflow is the same automation you'd build for yourself, just created as Team instead of Personal. There's no separate builder- you pick the owner in the same editor, at creation time, and Proliferate changes where it runs and who can touch it.
Run in: Personal vs Team picker
The workflow editor's 'Run as' popover with Personal and Team options, Team showing 'Organization cloud' as its target.
What's different about Team
- Where it runs. Team automations always run in your organization's cloud. There's no local option, since the whole point is that it doesn't depend on any one person's machine.
- Who can manage it. Today, team workflows are an admin tool end to end: creating, editing, running, and pausing one all require an organization admin role. The desktop app only shows the Team workflows list to admins.
- What it needs first. The organization needs a cloud environment already configured for the target repository. If one isn't set up yet, the editor's target picker offers a Set up cloud shortcut straight into that repo's cloud settings.
Everything else- the prompt, the schedule, the agent and model, the run history- works exactly like a personal automation. Broader "any teammate can trigger it" access is the natural next step here, but isn't in the product yet.
Good candidates
Start with workflows that are frequent, bounded, and easy for the whole team to review:
- Triage incoming issues.
- Prepare daily changelogs.
- Fix flaky tests.
- Draft small migrations.
- Run repeatable code review passes.
For work that's really just yours, start with a personal automation instead. The owner is locked in when you create it, so if you later want to share one with the team, recreate it as Team rather than looking for a toggle on the existing one.