Mechanism: Tasks execute in the cloud using a team service account and configured app connections, while workspace permissions govern who can create teams and manage automations. The documented tasks run in the cloud with a team service account and configured app connections. Administrators control who may create teams and manage team automations; configured connections determine which external accounts a task uses. The documentation gives an engineering example: gathering what shipped and what is blocked for a weekly update, with teammates able to review results and change the next update’s scope.
Why now: The announcement frames the capability around recurring engineering coordination, a workflow where information arrives across people and connected applications. The shift is from an individual asking for a periodic summary to a team maintaining a repeatable, reviewable update loop.
First implication: Team-level scheduled work can make review and correction part of the workflow instead of leaving an individual to maintain a recurring prompt. This implication follows from the shared setup and review described in the source; it is not evidence that the generated reports are accurate or save time.
Evidence boundary: The public Enterprise documentation describes configuration, permissions, connections, and illustrative use cases; it does not provide adoption, availability by plan, reliability, or outcome measurements. Treat the examples as documented intended workflows, not demonstrated performance.
First watch condition: Watch whether teams can reliably correct a recurring report and have that change persist in later runs, while keeping its connected-account access governed. The source says teammates can change what the next update covers, but does not detail the correction mechanism or its controls.