Short answer
Asana has announced a more operational job for AI Teammates: inspecting the rules in a project or portfolio, explaining what they do, surfacing paused or failing rules, and drafting a new or updated rule from a plain-English request. A person reviews the setup before it is published. For teams with a sprawling automation library, this could shorten audits and troubleshooting. It is not a reason to hand workflow governance to an agent.
What changed
AI Teammates have moved closer to Asana's rule layer. Users can ask which rules exist in a project or portfolio, what each rule does, whether it is paused or hitting errors, and what happened the last time it ran. A Teammate can also translate a workflow request into a proposed rule or rule change. The proposal stays behind a review step until a person chooses to publish it.
Why now
Asana is expanding AI Teammates from task-level collaboration into the systems that route work. Its help center says broader access to advanced AI capabilities begins in August 2026 when Asana AI is enabled, with usage drawn from a shared organization-level request pool. Because account-level access and usage can vary, customers should confirm their exact rollout and limits before building an operating process around it.
Who should care
Asana administrators, operations leads, PMO teams, and business systems owners with enough rules that ownership, troubleshooting, and cleanup have become recurring work. A small team with a handful of simple automations can probably keep using the standard rule builder.
Why it matters
Automation debt is easy to miss. Rules accumulate, owners change, and one paused or brittle rule can quietly break a handoff. A conversational inventory could shorten the path from “something stopped working” to the exact rule that needs attention. Plain-English drafting may also reduce setup time. The real value is fewer hours spent tracing and rebuilding workflows, not the novelty of asking AI to do it.
What this does not change
A proposed rule is not a tested rule. AI Teammates do not remove the need to check permissions, downstream effects, failure states, ownership, and rollback steps. Asana's public materials also leave account-specific availability and usage limits to the customer's plan and admin settings. Confirm access in the admin console before treating this as a standard capability.
Worthd take
This matters more than another AI writing feature because it touches the operational layer. Use it as a rule auditor and a builder's assistant. Let it find problems and prepare a first draft. Keep publishing rights, production checks, and accountability with the person who owns the workflow.
What to check next
- Choose one project with known rule sprawl.
- Ask the Teammate to inventory the rules, their status, and the last run.
- Compare its explanation with the rule builder before trusting the summary.
- Draft one low-risk change and review every trigger, condition, and action.
- Confirm who can publish rules and who owns failures.
- Measure audit and setup time saved for 30 days before expanding the process.
Open the official announcement Read the supporting documentation
Source review completed July 26, 2026.