The documentation also describes a configured execution path rather than an unbounded chat handoff.
First implication: Teams considering this workflow need to review the configured identity’s repository and connector access, not assume the requester’s personal permissions carry over.
Thesis
Delegations makes the handoff surface for coding work broader, while leaving execution identity and compute under explicit configuration.
Observed facts
Factory documentation says Droid work can be delegated from Slack, Linear, and Jira by mentioning Factory or assigning an issue.
1For shared delegations, administrators configure instructions, plugins, service-account identity, and compute; Slack direct messages use the sender’s personal identity and connectors.
1The documentation marks Microsoft Teams as in development.
1Factory recommends starting with a small, reviewable task specifying repository, desired outcome, and verification.
1
Mechanism
For shared delegations, an administrator configures instructions, plugins, a service-account identity, and compute; Slack direct messages instead use the sender’s personal identity and connectors.
Why now
Teams can route requests from tools where issues and coordination already live, but the documentation’s integration status makes precise availability reporting important.
Implications
Teams considering this workflow need to review the configured identity’s repository and connector access, not assume the requester’s personal permissions carry over.
Evidence boundary
The supplied Factory documentation describes setup and behavior; it does not provide adoption, task-success, or performance metrics, and it does not establish that Teams is generally available.
Watch conditions
Check whether Factory changes the Microsoft Teams status from “In development” and documents its actual delegation behavior.