Loading live status…
Loading live status…
Asana turned on Agentic Work Management for paid plans, launched three new products, renamed Rules to Automations and changed how rule permissions work. Here is everything it shipped in August and September, plus the outages worth knowing about.
Asana spent most of 2026 promising an "operating system for human-agent teams". In the second half of September it shipped most of it. Within about two weeks it switched on Agentic Work Management for paying customers, launched three new products and rebuilt its automation engine. It also reported its second-quarter results and changed the chair of its board.
Here is what arrived, in date order. Dates come from Asana's own announcements in its community forum and newsroom, linked at the bottom.
August was quiet next to September. The notable launches:
| Date | What shipped |
|---|---|
| 17 August | @mention Asana in Slack. Mention @asana in a Slack thread to turn the thread into a task, or to ask questions such as who owns a piece of work. Answers come back privately first and respect Asana permissions. Asana says it works on every tier, from Personal to Enterprise+. A Slack workspace admin may have to enable the app_mention scope. |
| 21 August | Rich text in custom fields, with headings, lists, links and images. Asana also added text highlighting, syntax highlighting in its editors, subtasks in the My Tasks grid, and a second version of scheduled triggers that runs scheduled rules on tasks already in a project. |
The August release notes, published on 29 September, also list a desktop app update (2.7.2) with fixes for malicious-link handling and argument-injection risks. If your team uses the desktop app, check that it has updated.
| Date | What shipped |
|---|---|
| 9 September | HIPAA support for Asana Gov. A super admin accepts a Business Associate Agreement in the admin console. HIPAA-enabled domains then hide sensitive details in notifications, turn off third-party integrations and personal access tokens by default, and restrict AI features. |
| 17 September | Agentic Work Management is live. It bundles more than 30 prebuilt AI Teammates, Asana Dash (an "AI chief of staff") and AI Studio into the paid plans. |
| 21 September | Rules become Automations, with a new builder. One automation can now act across tasks, projects and portfolios. Existing rules keep running without changes. |
| 22 September | Asana Service Management, for internal requests to IT, HR, facilities, legal and finance. |
| 24 September | Command by Asana, a planning system for product and engineering teams that works with coding agents. |
| 28 September | Asana Client Management is generally available, for agencies and professional services firms. |
| 30 September | Rules now run with their owner's current permissions. |
Asana's quarterly release roundup, posted on 30 September, also lists round-robin assignment in rules for high-volume requests, Pages (formerly Notes), and a redesigned sidebar and navigation. The forum also announced threaded comments this month.
The three new products and the AI pricing behind them are covered in our Agentic Work Management post.
The quietest announcement matters most for day-to-day reliability. From 30 September, automation rules run with their owner's permissions at the moment the rule fires, not the permissions the owner had when they created the rule. Asana says the change has already reached every user.
The security reason is sound: someone who has left a project should not keep acting in it through old automations. The side effect is that rules can pause or fail when their owner loses access, for example after a role change, leaving a team or being removed from a project. Asana's advice is to restore the owner's access or have a project admin take over the rule. Bundle rules, AI Studio rules and My Tasks rules are not affected.
If an automation stops firing this week, check who owns it before assuming Asana is down.
Asana's status page and the postmortem it published report several incidents this month:
Two incidents fell on launch days, but Asana has not linked either one to a launch. Two of the four happened in the EU region, and two involved automations or the API rather than the web app. Those failures are easy to miss because the Asana interface still loads while integrations and rules fail in the background.
When something in Asana looks broken, Asana's live status on isuptime checks its status feed every few minutes, alongside the other 102 services we monitor.
Sources
Checked continuously against each provider's own status feed.